public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: linux-mips@linux-mips.org, Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <tudor.ambarus@microchip.com>,
	Richard Weinberger <richard@nod.at>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mtd@lists.infradead.org,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Ben Dooks <ben-linux@fluff.org>, Jamie Iles <jamie@jamieiles.com>,
	Robert Jarzmik <robert.jarzmik@free.fr>,
	Daniel Mack <daniel@zonque.org>
Subject: Re: [PATCH 0/3] mtd: rawnand: gpio: Convert to exec_op()
Date: Wed, 3 Jun 2020 17:13:29 +0200	[thread overview]
Message-ID: <20200603171329.25d62424@xps13> (raw)
In-Reply-To: <20200603150746.1423257-1-boris.brezillon@collabora.com>


Boris Brezillon <boris.brezillon@collabora.com> wrote on Wed,  3 Jun
2020 17:07:43 +0200:

> Hello,
> 
> A bit of context to explain the motivation behind those conversions
> I've been sending for the last few weeks. The raw NAND subsystem
> carries a lot of history which makes any rework not only painful, but
> also subject to regressions which we only detect when someone dares to
> update its kernel on one of those ancient HW. While carrying drivers
> for old HW is not a problem per se, carrying ancient and unmaintained
> drivers that are not converted to new APIs is a maintenance burden,
> hence this massive conversion attempt I'm conducting here.
> 
> So here is a series converting the GPIO NAND controller driver to
> exec_op(). I hope I'll find someone to test those changes, but if
> there's no one still having access to this HW or no interest in keeping
> it supported in recent kernel versions, we should definitely consider
> removing the driver instead.
> 
> Regards,
> 
> Boris
> 
> Boris Brezillon (3):
>   mtd: rawnand: gpio: Inherit from nand_controller
>   mtd: rawnand: gpio: Implement exec_op()
>   mtd: rawnand: gpio: Get rid of the legacy interface implementation
> 
>  drivers/mtd/nand/raw/gpio.c | 116 ++++++++++++++++++++++++++++--------
>  1 file changed, 91 insertions(+), 25 deletions(-)
> 

Looks fine too!

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

      parent reply	other threads:[~2020-06-03 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 15:07 [PATCH 0/3] mtd: rawnand: gpio: Convert to exec_op() Boris Brezillon
2020-06-03 15:07 ` [PATCH 1/3] mtd: rawnand: gpio: Inherit from nand_controller Boris Brezillon
2020-06-15  9:00   ` Miquel Raynal
2020-06-03 15:07 ` [PATCH 2/3] mtd: rawnand: gpio: Implement exec_op() Boris Brezillon
2020-06-15  9:00   ` Miquel Raynal
2020-06-03 15:07 ` [PATCH 3/3] mtd: rawnand: gpio: Get rid of the legacy interface implementation Boris Brezillon
2020-06-15  9:00   ` Miquel Raynal
2020-06-03 15:13 ` Miquel Raynal [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=20200603171329.25d62424@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=ben-linux@fluff.org \
    --cc=boris.brezillon@collabora.com \
    --cc=daniel@zonque.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=jamie@jamieiles.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ralf@linux-mips.org \
    --cc=richard@nod.at \
    --cc=robert.jarzmik@free.fr \
    --cc=tudor.ambarus@microchip.com \
    --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