[PATCH master 1/2] Documentation: migration-guides: add heading for v2026.09.0

[PATCH master 1/2] Documentation: migration-guides: add heading for v2026.09.0

[Ahmad Fatoum]

Otherwise each entry is shown at the same level as the other releases.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/migration-guides/migration-2026.09.0.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/migration-guides/migration-2026.09.0.rst b/Documentation/migration-guides/migration-2026.09.0.rst
index 09ac5585e4d5..b1a20e894d47 100644
--- a/Documentation/migration-guides/migration-2026.09.0.rst
+++ b/Documentation/migration-guides/migration-2026.09.0.rst
@@ -1,3 +1,6 @@
+Release v2026.09.0
+==================
+
 Removal of deprecated CONFIG_BOOTM_OPTEE
 ----------------------------------------
 
-- 
2.47.3

[PATCH master 2/2] Documentation: migration-guides: turn migration-master into directory

[Ahmad Fatoum]

This allows us to avoid conflicts, especially when basing on master and
targeting merge into next.

An extra benefit is that the upcoming migration guides are no longer
hidden and thus easier to review after a local build.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/migration-guides/index.rst      |  1 +
 .../migration-guides/migration-master.rst     | 28 ++++++-------------
 .../migration-master/bootm-cmd.rst            | 20 +++++++++++++
 3 files changed, 30 insertions(+), 19 deletions(-)
 create mode 100644 Documentation/migration-guides/migration-master/bootm-cmd.rst

diff --git a/Documentation/migration-guides/index.rst b/Documentation/migration-guides/index.rst
index 5e1a0cfbc7a0..ded638639e1e 100644
--- a/Documentation/migration-guides/index.rst
+++ b/Documentation/migration-guides/index.rst
@@ -12,3 +12,4 @@ causes build errors is generally out-of-scope for these documents.
    :glob:
 
    migration-20*
+   migration-master
diff --git a/Documentation/migration-guides/migration-master.rst b/Documentation/migration-guides/migration-master.rst
index 715edd5934c0..a5ca0a7f3b46 100644
--- a/Documentation/migration-guides/migration-master.rst
+++ b/Documentation/migration-guides/migration-master.rst
@@ -1,22 +1,12 @@
-:orphan:
+Pending changes
+===============
 
-Removal of bootm -c/-s options
-------------------------------
+This sections lists possibly backwards-incompatible changes that have been committed
+to the barebox source tree, but have not yet been included into a release.
+If you have concerns about any of them, now's a good time to reach out to the
+:ref:`mailing list <feedback>`.
 
-The :ref:`command_bootm` options ``-c`` and ``-s`` used to selectively
-enable checksum/hash and signature verification, respectively.
+.. toctree::
+   :glob:
 
-They have been removed in favor of the global toggle
-:ref:`global.bootm.verify <magicvar_global_bootm_verify>`.
-This can be restricted at build-time via setting ``CONFIG_BOOTM_FORCE_SIGNED_IMAGES``
-or loosened :ref:`at runtime <use_security-policies>`
-via setting ``SCONFIG_BOOT_UNSIGNED_IMAGES``.
-
-The removal is motivated by making it easier to reason about what the active
-verification level is, especially as there are now other uses for verified
-images like when :ref:`global.of.overlay.path <magicvar_global_of_overlay_path>`
-points at a FIT.
-
-Existing users, if any, will fail-secure: The command will now exit with a failure::
-
-  bootm: invalid option -- s
+   migration-master/*
diff --git a/Documentation/migration-guides/migration-master/bootm-cmd.rst b/Documentation/migration-guides/migration-master/bootm-cmd.rst
new file mode 100644
index 000000000000..d82748d4a377
--- /dev/null
+++ b/Documentation/migration-guides/migration-master/bootm-cmd.rst
@@ -0,0 +1,20 @@
+Removal of bootm -c/-s options
+------------------------------
+
+The :ref:`command_bootm` options ``-c`` and ``-s`` used to selectively
+enable checksum/hash and signature verification, respectively.
+
+They have been removed in favor of the global toggle
+:ref:`global.bootm.verify <magicvar_global_bootm_verify>`.
+This can be restricted at build-time via setting ``CONFIG_BOOTM_FORCE_SIGNED_IMAGES``
+or loosened :ref:`at runtime <use_security-policies>`
+via setting ``SCONFIG_BOOT_UNSIGNED_IMAGES``.
+
+The removal is motivated by making it easier to reason about what the active
+verification level is, especially as there are now other uses for verified
+images like when :ref:`global.of.overlay.path <magicvar_global_of_overlay_path>`
+points at a FIT.
+
+Existing users, if any, will fail-secure: The command will now exit with a failure::
+
+  bootm: invalid option -- s
-- 
2.47.3

Re: [PATCH master 1/2] Documentation: migration-guides: add heading for v2026.09.0

[Sascha Hauer]

On Thu, 15 Oct 2026 13:03:30 +0200, Ahmad Fatoum wrote:
> Otherwise each entry is shown at the same level as the other releases.
> 
> 

Applied, thanks!

[1/2] Documentation: migration-guides: add heading for v2026.09.0
      https://git.pengutronix.de/cgit/barebox/commit/?id=8ba0d28dcd92 (link may not be stable)
[2/2] Documentation: migration-guides: turn migration-master into directory
      https://git.pengutronix.de/cgit/barebox/commit/?id=a2af2723dbec (link may not be stable)

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

Re: [PATCH master 1/2] Documentation: migration-guides: add heading for v2026.09.0

[Sascha Hauer]

On Thu, 15 Oct 2026 13:03:30 +0200, Ahmad Fatoum wrote:
> Otherwise each entry is shown at the same level as the other releases.
> 
> 

Applied, thanks!

[1/2] Documentation: migration-guides: add heading for v2026.09.0
      https://git.pengutronix.de/cgit/barebox/commit/?id=8ba0d28dcd92 (link may not be stable)
[2/2] Documentation: migration-guides: turn migration-master into directory
      (no commit info)

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