From: Uladzimir Bely <ubely@ilbers.de>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] wic/plugins/bootimg-efi-isar: Use initrd from source params
Date: Thu, 01 Feb 2024 13:06:13 +0300 [thread overview]
Message-ID: <6b360e25686efe1ed78149b0a656a0c8b518ce48.camel@ilbers.de> (raw)
In-Reply-To: <adf12fcd61001276a1053737c225f5253f153bb2.camel@siemens.com>
On Thu, 2024-01-25 at 12:06 +0000, 'MOESSBAUER, Felix' via isar-users
wrote:
> On Thu, 2024-01-25 at 11:55 +0100, 'Quirin Gylstorff' via isar-users
> wrote:
> > From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> >
> > This fixes the issue that you can add a initrd with the source
> > params
> > but it will still boot the initial initrd.
> >
> > Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> > ---
> > meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/meta/scripts/lib/wic/plugins/source/bootimg-efi-
> > isar.py
> > b/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py
> > index b934d0c7..27d40756 100644
> > --- a/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py
> > +++ b/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py
> > @@ -185,7 +185,12 @@ class BootimgEFIPlugin(SourcePlugin):
> >
> > title = source_params.get('title')
> >
> > + temp_initrd = None
> > + if initrd:
> > + temp_initrd = initrd
>
> Why not simply temp_initrd = initrd ?
>
> Anyways, the logic itself is fine.
>
> Felix
>
The comment is not yet addresses, since the patch itself passes CI and
can be merged.
What would be better for us to do - merge it "as is", wait for v2, or
include changes proposed by Felix without waiting of v2?
> > kernel, initrd =
> > isar_get_filenames(get_bitbake_var("IMAGE_ROOTFS"))
> > + if temp_initrd:
> > + initrd = temp_initrd
> >
> > boot_conf = ""
> > boot_conf += "title %s\n" % (title if title else
> > "boot")
> > --
> > 2.43.0
> >
>
> --
> Siemens AG, Technology
> Linux Expert Center
>
>
prev parent reply other threads:[~2024-02-01 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 10:55 Quirin Gylstorff
2024-01-25 12:06 ` MOESSBAUER, Felix
2024-02-01 10:06 ` Uladzimir Bely [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=6b360e25686efe1ed78149b0a656a0c8b518ce48.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@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