From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users@googlegroups.com, "Kiszka,
Jan (CT RDA IOT SES-DE)" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2 0/3] minor fixes
Date: Tue, 28 Jul 2020 22:46:01 +0200 [thread overview]
Message-ID: <20200728224601.551f9888@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20200728162726.GP26707@yssyq.m.ilbers.de>
Baurzhan,
we do have CI runners as well and they fail on "next" because of
bullseye issues. It is nice to see you are merging stuff but please
share how you actually make that build.
Henning
On Tue, 28 Jul 2020 18:27:26 +0200
Baurzhan Ismagulov <ibr@radix50.net> wrote:
> On Mon, Mar 16, 2020 at 01:55:49PM +0100, Cedric Hombourger wrote:
> > 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
>
> Thanks, applied p1 and p2 to next.
>
> With kind regards,
> Baurzhan.
>
next prev parent reply other threads:[~2020-07-28 20:46 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 ` [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 [this message]
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=20200728224601.551f9888@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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