Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Arnd Bergmann <arnd@arndb.de>,
	 Randy Dunlap <rdunlap@infradead.org>,
	 Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	 linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/3] mtd: maps: remove AMD Élan specific drivers
Date: Wed, 27 May 2026 11:21:26 +0200	[thread overview]
Message-ID: <87fr3djjhl.fsf@bootlin.com> (raw)
In-Reply-To: <20260526103227.3152003-1-arnd@kernel.org> (Arnd Bergmann's message of "Tue, 26 May 2026 12:32:04 +0200")

Hi Arnd,

On 26/05/2026 at 12:32:04 +02, Arnd Bergmann <arnd@kernel.org> wrote:

> From: Arnd Bergmann <arnd@arndb.de>
>
> There are four MTD maps drivers that are used with AMD Élan SoCs.
> Since 486-class CPU support was removed in commit 8b793a92d862 ("x86/cpu:
> Remove M486/M486SX/ELAN support"), it is no longer possible to actually
> use these, so just remove the drivers entirely.

There were pending patches in my queue removing these, except nettel.c.

I fixed up this commit while applying and adapted it this way:

    Author: Arnd Bergmann <arnd@arndb.de>
    Date:   Tue May 26 12:32:04 2026 +0200

        mtd: maps: remove AMD Élan specific drivers
    
        There were four MTD maps drivers that were used with AMD Élan SoCs.
        Since 486-class CPU support was removed in commit 8b793a92d862 ("x86/cpu:
        Remove M486/M486SX/ELAN support"), it is no longer possible to actually
        use these. Three of them have already been removed, so remove the
        remaining driver entirely.
    
        Signed-off-by: Arnd Bergmann <arnd@arndb.de>
        [Miquel Raynal: Only NETtel was still in the tree, adapt the patch and the commit log]
        Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>

     drivers/mtd/maps/Kconfig  |   6 ---
     drivers/mtd/maps/Makefile |   1 -
     drivers/mtd/maps/nettel.c | 462 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
     3 files changed, 469 deletions(-)


Is it okay for you?

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2026-05-27  9:21 UTC|newest]

Thread overview: 6+ 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-05-26 10:32 ` [PATCH 3/3] mtd: maps: remove obsolete impa7 " Arnd Bergmann
2026-05-27  9:21 ` Miquel Raynal [this message]
2026-05-27  9:34   ` [PATCH 1/3] mtd: maps: remove AMD Élan specific drivers 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=87fr3djjhl.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --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