public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH 0/3] minor fixes
Date: Tue, 10 Mar 2020 17:04:31 +0100	[thread overview]
Message-ID: <1583856274-254-1-git-send-email-Cedric_Hombourger@mentor.com> (raw)

Three minor fixes for your review. The sshd-regen-keys patch is the same change I suggested
to Henning yesterday in a private conversation. I am including it here because my ci_build
completed just now and I am not sure Henning had a chance to do that given the time lapsed
between my suggestion and his submission to the list. Let me know if you are taking Henning's
patch instead (same change) and I will remove it from here (I am really including it here
because the ci_build run was done with all three patches).

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.

Cedric Hombourger (3):
  sshd-regen-keys: correct dependency on ssh daemon service
  linux-custom: support use of an arbitrary in-tree defconfig
  dpkg-raw: make sure templates are processed before do_install

 meta/classes/dpkg-raw.bbclass                                 | 4 ++++
 meta/recipes-kernel/linux/linux-custom.inc                    | 2 ++
 .../sshd-regen-keys/files/sshd-regen-keys.service             | 2 +-
 .../{sshd-regen-keys_0.2.bb => sshd-regen-keys_0.3.bb}        | 0
 4 files changed, 7 insertions(+), 1 deletion(-)
 rename meta/recipes-support/sshd-regen-keys/{sshd-regen-keys_0.2.bb => sshd-regen-keys_0.3.bb} (100%)

-- 
2.20.1


             reply	other threads:[~2020-03-10 16:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 16:04 Cedric Hombourger [this message]
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       ` [PATCH v2 0/3] minor fixes Cedric Hombourger
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=1583856274-254-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