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

[PATCH next] 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>
---
next has a migration entry that's not yet on master.
This adapts:
https://lore.kernel.org/barebox/20261015110335.2285479-2-a.fatoum@pengutronix.de/T/#u
to next, so we can avoid these conflicts in future.
---
 Documentation/migration-guides/index.rst      |  1 +
 .../migration-guides/migration-master.rst     | 35 +++++--------------
 .../migration-master/bootm-cmd.rst            | 20 +++++++++++
 .../migration-master/stm32mp-deep-probe.rst   |  6 ++++
 4 files changed, 36 insertions(+), 26 deletions(-)
 create mode 100644 Documentation/migration-guides/migration-master/bootm-cmd.rst
 create mode 100644 Documentation/migration-guides/migration-master/stm32mp-deep-probe.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 43d0b27bb0fe..a5ca0a7f3b46 100644
--- a/Documentation/migration-guides/migration-master.rst
+++ b/Documentation/migration-guides/migration-master.rst
@@ -1,29 +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
-
-Deep probe is now the default on STM32MP13 and STM32MP15
---------------------------------------------------------
-
-barebox now enables deep probe for every ``st,stm32mp1xx`` compatible, even
-over ``barebox,disable-deep-probe``. Report to the mailing list if that
-breaks your board.
+   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
diff --git a/Documentation/migration-guides/migration-master/stm32mp-deep-probe.rst b/Documentation/migration-guides/migration-master/stm32mp-deep-probe.rst
new file mode 100644
index 000000000000..8ff966a4dcf5
--- /dev/null
+++ b/Documentation/migration-guides/migration-master/stm32mp-deep-probe.rst
@@ -0,0 +1,6 @@
+Deep probe is now the default on STM32MP13 and STM32MP15
+--------------------------------------------------------
+
+barebox now enables deep probe for every ``st,stm32mp1xx`` compatible, even
+over ``barebox,disable-deep-probe``. Report to the mailing list if that
+breaks your board.
-- 
2.47.3