From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] Documentation: migration-2025.10.0: add guide
Date: Mon, 13 Oct 2025 16:09:56 +0200 [thread overview]
Message-ID: <20251013140957.8360-1-a.fatoum@pengutronix.de> (raw)
By looking through the changes sitting in master waiting for the next
releases, two potential breakages pop up. Mention them in the migration
guide.
Cc: Sascha Hauer <s.hauer@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
.../migration-guides/migration-2025.10.0.rst | 21 +++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 Documentation/migration-guides/migration-2025.10.0.rst
diff --git a/Documentation/migration-guides/migration-2025.10.0.rst b/Documentation/migration-guides/migration-2025.10.0.rst
new file mode 100644
index 000000000000..80f8f37cf475
--- /dev/null
+++ b/Documentation/migration-guides/migration-2025.10.0.rst
@@ -0,0 +1,21 @@
+Release v2025.10.0
+==================
+
+Rename in /dev
+--------------
+
+The i.MX SNVS device file is now simply called ``snvs`` instead of the
+previous unwieldy name derived from device tree,
+e.g., ``/dev/30370000.snvs@30370000:snvs-lpgpr.of0``.
+
+EEPROMs that are pointed at by a device tree alias do no longer have
+an extra 0 at the end, e.g., ``/dev/eeprom00`` has become ``/dev/eeprom0``.
+
+AM62L DT Bindings
+-----------------
+
+The SCMI clock IDs for the AM62L have changed in ARM Trusted Firmware,
+because the old assignment was not conforming to spec.
+
+barebox now requires TF-A to contain commit
+229d03adf ("PENDING: feat(ti): add missing scmi pds").
--
2.47.3
next reply other threads:[~2025-10-13 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 14:09 Ahmad Fatoum [this message]
2025-10-20 11:31 ` 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=20251013140957.8360-1-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