From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH master 1/4] common: boards: qemu: read the command line from the cmdline fw_cfg key
Date: Wed, 02 Sep 2026 10:25:26 +0200 [thread overview]
Message-ID: <178833752686.3041200.8010114679910080336.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260831132456.730833-1-a.fatoum@pengutronix.de>
On Mon, 31 Aug 2026 15:24:51 +0200, Ahmad Fatoum wrote:
> The /boot/qemu_fw_cfg script has a guard for /dev/fw_cfg.cmdline but reads
> /dev/fw_cfg.initrd, so global.linux.bootargs.dyn.qemu ends up holding
> initrd contents instead of the -append string.
>
>
Applied, thanks!
[1/4] common: boards: qemu: read the command line from the cmdline fw_cfg key
https://git.pengutronix.de/cgit/barebox/commit/?id=fb389727a6d6 (link may not be stable)
[2/4] efi: loader: fix EFI_EXIT2 tracing an uninitialized status
https://git.pengutronix.de/cgit/barebox/commit/?id=9517f3e5ae01 (link may not be stable)
[3/4] fs: efivarfs: initialize dummy data written on variable creation
https://git.pengutronix.de/cgit/barebox/commit/?id=fcbe297b3755 (link may not be stable)
[4/4] sandbox: actually build the assembly setjmp/longjmp/initjmp
https://git.pengutronix.de/cgit/barebox/commit/?id=a74f7d7f00a1 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-09-02 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 13:24 Ahmad Fatoum
2026-08-31 13:24 ` [PATCH master 2/4] efi: loader: fix EFI_EXIT2 tracing an uninitialized status Ahmad Fatoum
2026-08-31 13:24 ` [PATCH master 3/4] fs: efivarfs: initialize dummy data written on variable creation Ahmad Fatoum
2026-08-31 13:24 ` [PATCH master 4/4] sandbox: actually build the assembly setjmp/longjmp/initjmp Ahmad Fatoum
2026-09-02 8:25 ` Sascha Hauer [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=178833752686.3041200.8010114679910080336.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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