From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: wangmy@fujitsu.com, openembedded-core@lists.openembedded.org,
Wang Mingyu <wangmy@cn.fujitsu.com>
Subject: Re: [OE-core] [PATCH v2] systemd-boot: upgrade 256.8 -> 256.9
Date: Thu, 12 Dec 2024 10:30:38 +0200 [thread overview]
Message-ID: <Z1qfLjJ7OnXIFAK2@nuoska> (raw)
In-Reply-To: <CANNYZj86YOBLurL4n774DPS-GQeqSPv8Zzw4DOoGVi_a57pS+Q@mail.gmail.com>
Hi,
On Thu, Dec 12, 2024 at 08:58:51AM +0100, Alexander Kanavin wrote:
> On Thu, 12 Dec 2024 at 08:42, Mikko Rapeli via lists.openembedded.org
> <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> > > ...ystemd-boot-native_256.8.bb => systemd-boot-native_256.9.bb} | 0
> > > .../systemd/{systemd-boot_256.8.bb => systemd-boot_256.9.bb} | 0
> > > meta/recipes-core/systemd/systemd.inc | 2 +-
> > > .../recipes-core/systemd/{systemd_256.8.bb => systemd_256.9.bb} | 0
>
>
> > NACK: must also update systemd and systemd-boot-native recipe versions since
> > systemd, systemd-boot and systemd-boot-native all use systemd.inc.
>
> The patch actually does this. Is something still missing?
You're right and I was wrong, sorry. I guess v1 of the patch was in current
master-next which was missing systemd recipe update. Would be nice to
change patch title prefix from systemd-boot to systemd though.
Cheers,
-Mikko
next prev parent reply other threads:[~2024-12-12 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 0:48 [OE-core] [PATCH v2] barebox: upgrade 2024.10.0 -> 2024.12.0 wangmy
2024-12-12 0:49 ` [OE-core] [PATCH v2] systemd-boot: upgrade 256.8 -> 256.9 wangmy
2024-12-12 7:42 ` Mikko Rapeli
2024-12-12 7:58 ` Alexander Kanavin
2024-12-12 8:30 ` Mikko Rapeli [this message]
2024-12-17 7:35 ` [OE-core] [PATCH v2] barebox: upgrade 2024.10.0 -> 2024.12.0 Enrico Jörns
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=Z1qfLjJ7OnXIFAK2@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@cn.fujitsu.com \
--cc=wangmy@fujitsu.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