From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: bst@pengutronix.de
Subject: Re: [PATCH v2 0/3] commands: devlookup: add option to print kernel root option
Date: Mon, 07 Apr 2025 09:52:52 +0200 [thread overview]
Message-ID: <174401237287.1146547.10177156398576512536.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250404182345.2999795-1-a.fatoum@pengutronix.de>
On Fri, 04 Apr 2025 20:23:42 +0200, Ahmad Fatoum wrote:
> There exists currently no way to view the kernel root option that
> barebox would generate when instructed to via global.bootm.root_dev,
> but without actually mounting the file system.
>
> Add a new devlookup -k option that can print this. This can be useful in
> scripts that want to fixup the root line, so it's interpreted by the rdinit,
> but not by the kernel.
>
> [...]
Applied, thanks!
[1/3] commands: devlookup: factor out cmd_export_val
https://git.pengutronix.de/cgit/barebox/commit/?id=61a33875bc21 (link may not be stable)
[2/3] commands: findmnt: add support for exporting target as variable
https://git.pengutronix.de/cgit/barebox/commit/?id=f041cefa94f9 (link may not be stable)
[3/3] commands: devlookup: add option to print kernel root option
https://git.pengutronix.de/cgit/barebox/commit/?id=069bc37e0d23 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-04-07 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 18:23 Ahmad Fatoum
2025-04-04 18:23 ` [PATCH v2 1/3] commands: devlookup: factor out cmd_export_val Ahmad Fatoum
2025-04-04 18:23 ` [PATCH v2 2/3] commands: findmnt: add support for exporting target as variable Ahmad Fatoum
2025-04-04 18:23 ` [PATCH v2 3/3] commands: devlookup: add option to print kernel root option Ahmad Fatoum
2025-04-07 7:52 ` 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=174401237287.1146547.10177156398576512536.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=bst@pengutronix.de \
/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