From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 1/2] Add support for extlinux.conf
Date: Tue, 5 May 2026 12:49:08 +0200 [thread overview]
Message-ID: <4e34c9f9-816a-4242-a324-0f23505e9cc8@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvShGMqgQ+MHq46n0q_VhqscNz3wNbgnCDaF20n=T-M_aA@mail.gmail.com>
Hello Alexander,
On 5/5/26 12:47 PM, Alexander Shiyan wrote:
> Hello Ahmad.
>
> ...
>>> + if (e->append) {
>>> + char *append;
>>> +
>>> + /*
>>> + * The same rootfs image may be launched from eMMC or SD card.
>>> + * Remove any hardcoded root= parameter from "append" to avoid
>>> + * conflicts, then let barebox automatically add the correct
>>> + * root= (via global.bootm.appendroot) based on the boot device.
>>> + */
>>> + if (data.appendroot)
>>> + append = remove_param(e->append, "ROOT=");
> ...
>> I thus have a question to you: What happens if you drop remove_param()
>> completely? Sure we will have two root=, but the later gets precedence,
>> so your use case would continue to work without giving users a wrong
>> expectation.
>
> Yes, the second one takes priority.
> The second one is the one added via extlinux.conf APPEND option.
> In our case we need the first parameter, i.e. which comes from barebox
> when global.bootm.appendroot is toggled on.
Ack. Please check the series I Cc'd you on, which ensures that
global.bootm.appendroot applies _after_ extlinux.conf APPEND.
Thanks,
Ahmad
>
> Thanks!
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-05-05 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 13:28 Alexander Shiyan
2026-04-28 13:28 ` [PATCH v2 2/2] Documentation: add extlinux.conf support description Alexander Shiyan
2026-05-05 9:56 ` [PATCH v2 1/2] Add support for extlinux.conf Ahmad Fatoum
2026-05-05 10:47 ` Alexander Shiyan
2026-05-05 10:49 ` Ahmad Fatoum [this message]
2026-05-05 12:19 ` Alexander Shiyan
2026-05-05 12:22 ` Ahmad Fatoum
2026-05-05 12:44 ` Alexander Shiyan
2026-05-05 12:52 ` Ahmad Fatoum
2026-05-05 13:01 ` Alexander Shiyan
2026-05-05 13:04 ` Ahmad Fatoum
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=4e34c9f9-816a-4242-a324-0f23505e9cc8@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.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