From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Cc: u-boot-custodians@lists.denx.de, u-boot-board-maintainers@lists.denx.de
Subject: [ANN] U-Boot v2026.04 released
Date: Mon, 6 Apr 2026 12:00:20 -0600 [thread overview]
Message-ID: <20260406180020.GX41863@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 2394 bytes --]
Hey all,
It's time for the full release, and so here we are. I've tagged and
pushed everything out. This is another release that feels like it's just
good stable iterative progress on that last. The big change here is that
we resynced out libfdt code and finally device trees must really be
properly aligned. I am optimistic we have caught all the cases where
this was not true. But if you upgrade from v2026.01 and suddenly fail to
boot with little output, this is a very likely culprit.
We're continuing with a community meeting following the release and the
calendar link is
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MHYzYzQ1dWh2bnRjcm80czVmcDczYmhsNThfMjAyNjAxMjdUMTUwMDAwWiA4OWJlN2I4MTMxMzZiZWMwNmE4M2RlNGRhNTk3NDVmMGFiZDExYzFiODM2MDYxYWUwNmMxYzdkYmNkMThkZjQxQGc&tmsrc=89be7b813136bec06a83de4da59745f0abd11c1b836061ae06c1c7dbcd18df41%40group.calendar.google.com&scp=ALL
and once again this is the same time as the previous meeting. The
meeting details itself are:
https://meet.google.com/icv-nvmv-dbf
April 7th, 2025. 9am (GMT -06:00)
To join by phone:
https://tel.meet/icv-nvmv-dbf?pin=5493171900556
Condensing the changelog from the -rcs themselves:
- Our dts/upstream trees are synced to the v6.18-dts tag.
- As mentioned above, we've re-synced the libfdt code and now enforce
and require proper 8-byte alignment for the start of the device tree.
- Lots and lots of platform updates. Rather than call out what seems
like most modern SoCs, I'll let custodians reply if there's anything
specific they want to emphasize.
- A number of bugfixes for problems found by Smatch and Coverity Scan.
- We now support clang-format and prefer that over the old
scripts/Lindent option for formatting code.
- Numerous documentation updates.
- Many subsystems have also had a number of updates, and I'll again
leave it to the custodians to point out anything they'd like to here.
- We now have "allyesconfig" supported in CI. This isn't quite how the
Linux Kernel works (we do not assume 0 is a valid value for hex/int
questions, by default) but it's catching more issues now that weren't
before.
The merge window is now open, I'll be merging next to master shortly,
and we'll have our usual bi-weekly releases after -rc1 comes out in 3
weeks with the final release being on 06 July 2026.
Thanks all!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2026-04-06 18:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260406180020.GX41863@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot-board-maintainers@lists.denx.de \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.de \
/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