From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <dmitry.baryshkov@oss.qualcomm.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] uki.bbclass: fix building of UKI images with multiple initramfs fstypes
Date: Mon, 19 Jan 2026 10:05:50 +0100 [thread overview]
Message-ID: <DFSG2N779PI3.3DYP47ZXHVXAZ@bootlin.com> (raw)
In-Reply-To: <qatgc5yvubfyokn5iav6ftmwwx25j7bbn422u64g5v5xdu7pjr@nisbj4cwtbxt>
Hi,
On Mon Jan 19, 2026 at 7:46 AM CET, Dmitry Baryshkov via lists.openembedded.org wrote:
> On Wed, Jan 07, 2026 at 06:23:45AM +0200, Dmitry Baryshkov wrote:
>> If INITRAMFS_FSTYPES contains more than one entry, ukify build command
>> will fail as INITRD_ARCHIVE will contain extra strings. Use only the
>> first initramfs type, letting the user to specify other fstypes.
>>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>> ---
>> meta/classes-recipe/uki.bbclass | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>
> And gracious ping. This was sent almost two weeks ago with no feedback
> to it up to now.
This has passed testing, but due do intermittent issues on our test
infrastructure merging patches has slowed down. Reviews should be on their way
soon hopefully.
See https://wiki.yoctoproject.org/wiki/Weekly_Status.
Regards,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-19 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 4:23 [PATCH] uki.bbclass: fix building of UKI images with multiple initramfs fstypes Dmitry Baryshkov
2026-01-19 6:46 ` Dmitry Baryshkov
2026-01-19 9:05 ` Antonin Godard [this message]
2026-01-19 18:25 ` [OE-core] " Paul Barker
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=DFSG2N779PI3.3DYP47ZXHVXAZ@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
/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