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 v2022.04 released
Date: Mon, 4 Apr 2022 10:32:53 -0400 [thread overview]
Message-ID: <20220404143253.GQ14476@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
Hey all,
It is release day and here is v2022.04. As a general reminder, there's
still many DM migrations that need to be done and while we try and have
a non-fatal warning message printed out when building a given platform,
some things can slip through the cracks. Checking out your boards
config file manually is probably a good idea and seeing if there's any
CONFIG_DM_xxx options that should get enabled.
Since the last time I iterated on new migration deadlines, there's now
CONFIG_TIMER is deprecated, and DM_SERIAL and DM_SCSI need to be migrated.
I've been making more progress on CONFIG migration but more help here is
always appreciated. And related, buildman needs a little help moving
away from needing to use tools/genboards.py to make the old old old
style boards.cfg file and instead use kconfiglib directly.
In terms of a changelog,
git log --merges v2022.04-rc5..v2022.04
contains what I've pulled since the last RC or:
git log --merges v2022.01..v2022.04
for changes since the last full release. As always, more details in
pull requests (or the tags referenced by them) will result in more
details here.
With this, the merge window is now open and I'll be merging in the next
branch shortly. v2022.07 is scheduled for release on Monday, July
4th 2022 and the merge window closes on April 25th. Thanks all!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
reply other threads:[~2022-04-04 14:33 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=20220404143253.GQ14476@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).