From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 2/2] Documentation: migration-guides: 2026.01.0: clarify fsdev linux.bootargs change
Date: Wed, 25 Feb 2026 16:10:05 +0100 [thread overview]
Message-ID: <20260225151007.412926-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20260225151007.412926-1-a.fatoum@pengutronix.de>
The entry is a bit confusing and it's not clearly spelt out that this
doesn't affect global.linux.bootargs, so make this clearer.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
.../migration-guides/migration-2026.01.0.rst | 23 ++++++++++---------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/Documentation/migration-guides/migration-2026.01.0.rst b/Documentation/migration-guides/migration-2026.01.0.rst
index 931972901695..b40d125195a7 100644
--- a/Documentation/migration-guides/migration-2026.01.0.rst
+++ b/Documentation/migration-guides/migration-2026.01.0.rst
@@ -12,21 +12,22 @@ like the in-tree boards are already doing.
Filesystems
-----------
-``{linux.bootargs}`` is replaced with ``root={linux.bootargs.root} {linux.bootargs.rootopts}``
+The ``linux.bootargs`` file system device parameter (e.g. ``ext40.linux.bootargs``)
+has been replaced by the two variables ``${fsdev}.linux.bootargs.root`` and
+``${fsdev}.linux.bootargs.rootopts``, splitting the previous bootargs
+into three parts. For example, the previous::
-The variable linux.bootargs has been replaced by the two variables
-linux.bootargs.root and linux.bootargs.rootopts, splitting the previous bootargs
-into three parts. A nonexistent fixed "root=", then the root filesystem and then
-additional optional params for this particular filesystem.
-
-for example the previous::
-
- linux.bootargs="root=/dev/nfs nfsroot=192.168.1.1:/rootfs"
+ ext40.linux.bootargs="root=/dev/nfs nfsroot=192.168.1.1:/rootfs"
becomes::
- linux.bootargs.root="/dev/nfs"
- linux.bootargs.rootopts="nfsroot=192.168.1.1:/rootfs"
+ ext40.linux.bootargs.root="/dev/nfs"
+ ext40.linux.bootargs.rootopts="nfsroot=192.168.1.1:/rootfs"
+
+Scripts that access these parameters will need to be adapted to replace
+``{linux.bootargs}`` with ``root={linux.bootargs.root} {linux.bootargs.rootopts}``.
+
+``global.linux.bootargs.*`` is unaffected by this change.
Boards
------
--
2.47.3
next prev parent reply other threads:[~2026-02-25 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 15:10 [PATCH master 1/2] Documentation: migration-guides: split off 2026.02.0 into own file Ahmad Fatoum
2026-02-25 15:10 ` Ahmad Fatoum [this message]
2026-02-26 12:01 ` Sascha Hauer
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=20260225151007.412926-2-a.fatoum@pengutronix.de \
--to=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