From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Greg Ungerer" <gregungerer@westnet.com.au>,
"Arnd Bergmann" <arnd@kernel.org>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
"Pengpeng Hou" <pengpeng@iscas.ac.cn>
Subject: Re: [PATCH 2/3] mtd: maps: remove uclinux map driver
Date: Fri, 26 Jun 2026 16:21:50 +0200 [thread overview]
Message-ID: <87ik75l6v5.fsf@bootlin.com> (raw)
In-Reply-To: <f3e984cd-0614-48d1-b03f-e0670b87e282@app.fastmail.com> (Arnd Bergmann's message of "Thu, 25 Jun 2026 16:10:54 +0200")
Hello Arnd,
>> No out of tree code is required. Most of the ColdFire defconfigs have
>> CONFIG_MTD_UCLINUX enabled, since it is commonly used.
>
> I see, this is surprising from reading the source and
> git history, but I can see exactly how it got there.
>
> So this is not actually a device but rather a replacement
> for CONFIG_BLK_DEV_INITRD that does can work with CONFIG_BLOCK=y,
> right?
>
>> Can we get this reverted?
>
> Yes, of course. Miquel/Richard/Vignesh, should I send a revert or
> can you just apply one with Greg's explanation and my Ack?
I'll try to come up with something next week :-)
Thanks,
Miquèl
next prev parent reply other threads:[~2026-06-26 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 10:32 [PATCH 1/3] mtd: maps: remove AMD Élan specific drivers Arnd Bergmann
2026-05-26 10:32 ` [PATCH 2/3] mtd: maps: remove uclinux map driver Arnd Bergmann
2026-06-25 12:07 ` Greg Ungerer
2026-06-25 14:10 ` Arnd Bergmann
2026-06-25 22:15 ` Greg Ungerer
2026-06-26 12:18 ` Andy Shevchenko
2026-06-26 14:21 ` Miquel Raynal [this message]
2026-05-26 10:32 ` [PATCH 3/3] mtd: maps: remove obsolete impa7 " Arnd Bergmann
2026-05-27 9:21 ` [PATCH 1/3] mtd: maps: remove AMD Élan specific drivers Miquel Raynal
2026-05-27 9:34 ` Arnd Bergmann
2026-05-27 12:31 ` Miquel Raynal
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=87ik75l6v5.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=gregungerer@westnet.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pengpeng@iscas.ac.cn \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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