From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH v2 0/3] minor fixes
Date: Mon, 16 Mar 2020 13:55:49 +0100 [thread overview]
Message-ID: <1584363352-866-1-git-send-email-Cedric_Hombourger@mentor.com> (raw)
In-Reply-To: <20200316133934.223e4a0b@md1za8fc.ad001.siemens.net>
Three minor fixes for your review.
Have the sshd-regen-keys services depend on ssh.service instead of sshd.service (so we
rely on its official name, not its alias)
The change to linux-custom allows use of named defconfigs living in the kernel tree. I realized
this was not correctly handled while building a kernel for MPSOC (xilinx_zynqmp_defconfig)
Lastly, the dpkg-raw class was modified so it may be used together with the very convenient
templating class.
Changes in v2:
sshd-regen-keys: amend commit message as suggested by Henning
Cedric Hombourger (3):
sshd-regen-keys: sshd-regen-keys: depend on ssh.service instead of sshd.service
linux-custom: support use of an arbitrary in-tree defconfig
dpkg-raw: make sure templates are processed before do_install
--
2.20.1
next prev parent reply other threads:[~2020-03-16 12:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 16:04 [PATCH " Cedric Hombourger
2020-03-10 16:04 ` [PATCH 1/3] sshd-regen-keys: correct dependency on ssh daemon service Cedric Hombourger
2020-03-11 8:34 ` Henning Schild
2020-03-11 8:50 ` Henning Schild
2020-03-11 9:32 ` Jan Kiszka
2020-03-11 10:04 ` Henning Schild
2020-03-12 13:50 ` Gylstorff Quirin
2020-03-16 12:39 ` Henning Schild
2020-03-16 12:55 ` Cedric Hombourger [this message]
2020-03-16 12:55 ` [[PATCH v2] 1/3] sshd-regen-keys: depend on ssh.service instead of sshd.service Cedric Hombourger
2020-03-16 12:55 ` [[PATCH v2] 2/3] linux-custom: support use of an arbitrary in-tree defconfig Cedric Hombourger
2020-03-16 12:55 ` [[PATCH v2] 3/3] dpkg-raw: make sure templates are processed before do_install Cedric Hombourger
2020-04-10 12:11 ` Baurzhan Ismagulov
2020-04-14 6:02 ` Jan Kiszka
2020-04-17 15:30 ` Baurzhan Ismagulov
2020-04-17 15:46 ` Jan Kiszka
2020-07-28 16:27 ` [PATCH v2 0/3] minor fixes Baurzhan Ismagulov
2020-07-28 20:46 ` Henning Schild
2020-07-30 16:08 ` Baurzhan Ismagulov
2020-03-10 16:04 ` [PATCH 2/3] linux-custom: support use of an arbitrary in-tree defconfig Cedric Hombourger
2020-03-10 16:04 ` [PATCH 3/3] dpkg-raw: make sure templates are processed before do_install Cedric Hombourger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1584363352-866-1-git-send-email-Cedric_Hombourger@mentor.com \
--to=cedric_hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox