From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: DM_MMC, BLK
Date: Thu, 25 Feb 2021 13:42:50 -0500 [thread overview]
Message-ID: <20210225184250.GZ10169@bill-the-cat> (raw)
In-Reply-To: <2c2b97f1-0bdc-cbdb-7f09-da6e53ece2d3@gmx.de>
On Thu, Feb 25, 2021 at 06:47:55PM +0100, Heinrich Schuchardt wrote:
> On 2/24/21 10:32 PM, Tom Rini wrote:
> > On Wed, Feb 24, 2021 at 10:28:31PM +0100, Heinrich Schuchardt wrote:
> >
> > > Hello Tom,
> > >
> > > migrating to CONFIG_DM_MMC was scheduled for release v2019.04. But some
> > > board maintainers simply don't care.
> > >
> > > We have quite a lot of boards like cm_t335, draco, etamin, rastaban,
> > > thuban, pxm2, vinco which compile when setting CONFIG_DM_MMC and CONFIG_BLK.
> > >
> > > Shall we switch all boards that compile with these settings?
> >
> > Please see
> > https://patchwork.ozlabs.org/project/uboot/list/?series=230325
>
> There are other parts concerning block devices needing clean up. E.g the
> usage of HAVE_BLOCK_DEVICE in disk/.
>
> Having all these changes collected in a next branch would be helpful.
I've got various rebasing branches up with these removals (and some
temporary merges) currently under WIP/make-DM_xxx-fatal. I will be
opening next fairly soon.
--
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/20210225/089e64fd/attachment.sig>
prev parent reply other threads:[~2021-02-25 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 21:28 DM_MMC, BLK Heinrich Schuchardt
2021-02-24 21:32 ` Tom Rini
2021-02-24 22:15 ` Heinrich Schuchardt
2021-02-24 23:10 ` Simon Glass
2021-02-25 17:47 ` Heinrich Schuchardt
2021-02-25 18:42 ` Tom Rini [this message]
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=20210225184250.GZ10169@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