mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH] Documentation: migration-2025.05.0: note compressed kernel regression
Date: Thu, 12 Jun 2025 11:16:11 +0200	[thread overview]
Message-ID: <20250612091611.11281-1-a.fatoum@barebox.org> (raw)

The breakage is annoying enough that it deserves being pointed out
explicitly.

Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
There is nothing I want to add for migration2-2025.06.0.
---
 .../migration-guides/migration-2025.05.0.rst          | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/Documentation/migration-guides/migration-2025.05.0.rst b/Documentation/migration-guides/migration-2025.05.0.rst
index 82b9fcb8e53f..f22c9f7c02c5 100644
--- a/Documentation/migration-guides/migration-2025.05.0.rst
+++ b/Documentation/migration-guides/migration-2025.05.0.rst
@@ -92,6 +92,11 @@ Build system
 Bisectability
 -------------
 
-Many users of ``read*_poll_is_timeout`` are broken between
-``554bbc479c09..dea0ad02bbd6``, which can falsify git bisect
-results.
+Following regressions had a wider impact and could falsify
+falsify git bisect results:
+
+* Many users of ``read*_poll_is_timeout`` are broken between
+  ``554bbc479c09..dea0ad02bbd6``.
+
+* Handling of compressed kernel images on ARM64/RISC-V was broken between
+  ``a1248198fa3a..95aeb8d47d10``.
-- 
2.39.5




             reply	other threads:[~2025-06-12 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  9:16 Ahmad Fatoum [this message]
2025-06-17  7:14 ` 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=20250612091611.11281-1-a.fatoum@barebox.org \
    --to=a.fatoum@barebox.org \
    --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