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.01-rc5 released
Date: Mon, 22 Dec 2025 16:31:38 -0600 [thread overview]
Message-ID: <20251222223138.GD847766@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
Hey all,
It is once again release day, and so here is -rc5. Given the upcoming
holidays between here and release day in much of the world, I'm hoping
for very little changes between here and release. I'm quite happy to see
pull requests for the next branch of changes people have outstanding,
and as always if people know of regression fixes that haven't been
picked up please point them out to me.
We're continuing with a community meeting following the release and the
calendar link is
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=ZGNsNTh2YWQ2YTB0ajAzZXRkdDVhdjFuNmpfMjAyNTEwMjhUMTUwMDAwWiA4OWJlN2I4MTMxMzZiZWMwNmE4M2RlNGRhNTk3NDVmMGFiZDExYzFiODM2MDYxYWUwNmMxYzdkYmNkMThkZjQxQGc&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/btj-wgcg-euw
December 23rd, 2025. 9am (GMT -06:00)
To join by phone:
https://meet.google.com/tel/btj-wgcg-euw?pin=1307528552322&hs=1
In terms of a rough changelog:
- Assorted minor to us security fixes
- Scattered code corrections
- Some rockchip and stm32 and TI specific fixes.
This is the last scheduled rc before the final release which will be on
05 January 2026.
Thanks all!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2025-12-22 22:31 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=20251222223138.GD847766@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;
as well as URLs for NNTP newsgroup(s).