From: Paul Barker <paul@pbarker.dev>
To: dmitry.baryshkov@oss.qualcomm.com,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] uki.bbclass: fix building of UKI images with multiple initramfs fstypes
Date: Fri, 23 Jan 2026 12:53:48 +0000 [thread overview]
Message-ID: <b83b668e61d0189cc1df1569eb39982bf0565a7a.camel@pbarker.dev> (raw)
In-Reply-To: <20260120024313.3467088-1-dmitry.baryshkov@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Tue, 2026-01-20 at 04:43 +0200, Dmitry Baryshkov via
lists.openembedded.org 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 in
> INITRAMFS_FSTYPES.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Hi Dmitry,
The implementation now looks good. The commit message needs a little
rewording, we need to note that INITRD_ARCHIVE is now gone so that it's
easier to notice this change when we're compiling release notes.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2026-01-23 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 2:43 [PATCH v2] uki.bbclass: fix building of UKI images with multiple initramfs fstypes Dmitry Baryshkov
2026-01-23 12:53 ` Paul Barker [this message]
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=b83b668e61d0189cc1df1569eb39982bf0565a7a.camel@pbarker.dev \
--to=paul@pbarker.dev \
--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