public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [ANN] U-Boot v2021.04-rc4 released
Date: Wed, 17 Mar 2021 09:28:51 -0400	[thread overview]
Message-ID: <20210317132851.GG1310@bill-the-cat> (raw)
In-Reply-To: <20210317132145.GA2369@localhost>

On Wed, Mar 17, 2021 at 09:21:45AM -0400, Trevor Woerner wrote:
> On Wed 2021-03-17 @ 08:55:59 AM, Tom Rini wrote:
> > On Wed, Mar 17, 2021 at 01:13:57PM +0100, Marek Vasut wrote:
> > > On 3/15/21 5:07 PM, Tom Rini wrote:
> > > > Hey all,
> > > > 
> > > > It's release day, and here's v2021.04-rc4.  Not a whole lot of change
> > > > since last time in master, and -next has been and is still open.  I just
> > > > want to repeat a few things from -rc3:
> > > > 
> > > > - We've moved from "gitlab.denx.de" (and also "git.denx.de") to
> > > >    "source.denx.de", please make sure to update your scripts and tools
> > > >    and so forth.  If you send me pull requests, now is a good time to
> > > >    switch to url/pushurl if you haven't already.
> > > > - Once v2021.04 is released I will be pushing a large number of board
> > > >    removals for things that will be then 2 years past their "migrate this
> > > >    by ... or it might be removed" date which is also around 3 years total
> > > >    of notice.
> > > 
> > > Which ones ?
> > 
> > All of the ones I've sent out removal patches for over the last month,
> > CC'ing the maintainers.  That's basically:
> > https://patchwork.ozlabs.org/project/uboot/list/?series=228850
> > https://patchwork.ozlabs.org/project/uboot/list/?series=230325
> > along with I believe I need to v2 dropping some defconfigs for I believe
> > mx28evk once Stefano picks up Fabio's patch to update and maintain the
> > main defconfig (he already ack'd such a removal).
> 
> Ah okay, just DM_MMC for now, so the lpc32xx boards aren't on the block? yet.

I would emphasize that yet.  v2021.07 is just around the corner and
marks 3 years of DM_USB being a loud "please migrate me".  We're going
to be hitting that milestone every release in 2021.

> However, I am interested in preserving the olimex board (i.e.
> configs/mx23_olinuxino_defconfig). So I could take a look at that one first
> unless, Marek, you would like to take a look?

https://patchwork.ozlabs.org/project/uboot/patch/20210218233230.506201-2-festevam at gmail.com/
is likely a handy patch to look at for whomever is interested in the
board.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210317/297daab5/attachment.sig>

  reply	other threads:[~2021-03-17 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 16:07 [ANN] U-Boot v2021.04-rc4 released Tom Rini
2021-03-17 12:06 ` Trevor Woerner
2021-03-17 12:13 ` Marek Vasut
2021-03-17 12:55   ` Tom Rini
2021-03-17 13:21     ` Trevor Woerner
2021-03-17 13:28       ` Tom Rini [this message]
2021-03-17 13:30       ` Marek Vasut
2021-03-17 13:37       ` Fabio Estevam
2021-03-17 13:53         ` Trevor Woerner
2021-03-22  1:09         ` Trevor Woerner
2021-03-22  1:28           ` Tom Rini
2021-03-22  1:37             ` Trevor Woerner
2021-03-17 22:59     ` Jaehoon Chung

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=20210317132851.GG1310@bill-the-cat \
    --to=trini@konsulko.com \
    --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