[PATCH master 1/2] Documentation: migration-guides: split off 2026.02.0 into own file

[PATCH master 1/2] Documentation: migration-guides: split off 2026.02.0 into own file

[Ahmad Fatoum]

Having a single migration-master.rst turns out to be error prone, because
presumably git detects the rename of the last release and adds new
entries not to migration-master.rst after the rebase, but to the
migration guide for the former release.

This seems to have happend with commit 09663fb38ffd
("startup: attempt poweroff if no shell and nothing to do"),
so move it back into the correct file and while at it add a
migration-master.rst right away.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 .../migration-guides/migration-2026.01.0.rst          |  9 ---------
 .../migration-guides/migration-2026.02.0.rst          | 11 +++++++++++
 Documentation/migration-guides/migration-master.rst   |  1 +
 3 files changed, 12 insertions(+), 9 deletions(-)
 create mode 100644 Documentation/migration-guides/migration-2026.02.0.rst
 create mode 100644 Documentation/migration-guides/migration-master.rst

diff --git a/Documentation/migration-guides/migration-2026.01.0.rst b/Documentation/migration-guides/migration-2026.01.0.rst
index df7b3d6f497a..931972901695 100644
--- a/Documentation/migration-guides/migration-2026.01.0.rst
+++ b/Documentation/migration-guides/migration-2026.01.0.rst
@@ -36,12 +36,3 @@ ARM i.MX6 RIoTboard
 
 The barebox update handler has been changed to write barebox to the
 eMMC boot partitions rather than the user data area.
-
-CONFIG_SHELL_NONE
------------------
-
-If there's nothing to do for a shell-less barebox, it will now attempt
-to poweroff the system instead of busy-looping indefinitely.
-This changes behavior for systems that rely on a watchdog to reset
-a hanging barebox in this situation. If this breaks anything for you,
-please reach out.
diff --git a/Documentation/migration-guides/migration-2026.02.0.rst b/Documentation/migration-guides/migration-2026.02.0.rst
new file mode 100644
index 000000000000..80da34d32f5e
--- /dev/null
+++ b/Documentation/migration-guides/migration-2026.02.0.rst
@@ -0,0 +1,11 @@
+Release v2026.02.0
+==================
+
+CONFIG_SHELL_NONE
+-----------------
+
+If there's nothing to do for a shell-less barebox, it will now attempt
+to poweroff the system instead of busy-looping indefinitely.
+This changes behavior for systems that rely on a watchdog to reset
+a hanging barebox in this situation. If this breaks anything for you,
+please reach out.
diff --git a/Documentation/migration-guides/migration-master.rst b/Documentation/migration-guides/migration-master.rst
new file mode 100644
index 000000000000..8feca331c5d7
--- /dev/null
+++ b/Documentation/migration-guides/migration-master.rst
@@ -0,0 +1 @@
+:orphan:
-- 
2.47.3

[PATCH master 2/2] Documentation: migration-guides: 2026.01.0: clarify fsdev linux.bootargs change

[Ahmad Fatoum]

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

Re: [PATCH master 1/2] Documentation: migration-guides: split off 2026.02.0 into own file

[Sascha Hauer]

On Wed, 25 Feb 2026 16:10:04 +0100, Ahmad Fatoum wrote:
> Having a single migration-master.rst turns out to be error prone, because
> presumably git detects the rename of the last release and adds new
> entries not to migration-master.rst after the rebase, but to the
> migration guide for the former release.
> 
> This seems to have happend with commit 09663fb38ffd
> ("startup: attempt poweroff if no shell and nothing to do"),
> so move it back into the correct file and while at it add a
> migration-master.rst right away.
> 
> [...]

Applied, thanks!

[1/2] Documentation: migration-guides: split off 2026.02.0 into own file
      https://git.pengutronix.de/cgit/barebox/commit/?id=b25e4295954b (link may not be stable)
[2/2] Documentation: migration-guides: 2026.01.0: clarify fsdev linux.bootargs change
      https://git.pengutronix.de/cgit/barebox/commit/?id=aeca7cbbdd56 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>