From: Tom Rini <trini@konsulko.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
u-boot-custodians@lists.denx.de,
u-boot-board-maintainers@lists.denx.de
Subject: Re: [ANN] U-Boot v2021.07 released
Date: Tue, 6 Jul 2021 09:06:34 -0400 [thread overview]
Message-ID: <20210706130634.GP9516@bill-the-cat> (raw)
In-Reply-To: <CAHUNapR-_XPoQ7Cp95YiSNMUdjq6Mz6pjpgp2mkHMbxevt5RtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
On Tue, Jul 06, 2021 at 02:41:45AM -0400, Trevor Woerner wrote:
> On Mon, Jul 5, 2021 at 11:13 AM Tom Rini <trini@konsulko.com> wrote:
>
> > It is release day and here is the v2021.07 release.
> >
> > The merge window is once again open and I plan to tag -rc1 on Monday,
> > July 26th, bi-weekly -rcs thereafter and final release on October 4th,
> > 2021.
> >
> > I am merging the next branch to master shortly and will send a separate
> > email when that is done.
> >
>
> Is there something I forgot to do in order to get my lpc32xx series in?
> https://patchwork.ozlabs.org/project/uboot/list/?series=248264
A good question. I had hoped to get a chance to pickup platform stuff
for next, but did not. My plan right now is:
- General CI updates (now in)
- Update to gcc-11/clang-11 (I know clang-12 is out, but, one step at a
time) which I'm testing now.
- Platform updates
- Kick-around how USB_HOST is used, to deal with the DM_USB migration
deadline warning for Nokia N900
- Platform removals
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-07-06 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 15:13 [ANN] U-Boot v2021.07 released Tom Rini
2021-07-05 17:54 ` Tom Rini
2021-07-06 6:41 ` Trevor Woerner
2021-07-06 13:06 ` Tom Rini [this message]
2021-07-06 13:09 ` Trevor Woerner
2021-07-06 8:55 ` Wolfgang Denk
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=20210706130634.GP9516@bill-the-cat \
--to=trini@konsulko.com \
--cc=twoerner@gmail.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