[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA_RMS4HJ--eAwUoktMZS_rVS7+RhMhaYVPLGZmsXvcX6D2Ltw@mail.gmail.com>
Date: Fri, 10 Nov 2023 15:10:01 -0800
From: David Regan <dregan@...adcom.com>
To: William Zhang <william.zhang@...adcom.com>
Cc: David Regan <dregan@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
linux-mtd@...ts.infradead.org, f.fainelli@...il.com,
rafal@...ecki.pl, Joel Peshkin <joel.peshkin@...adcom.com>,
computersforpeace@...il.com,
Dan Beygelman <dan.beygelman@...adcom.com>,
frieder.schrempf@...tron.de, linux-kernel@...r.kernel.org,
vigneshr@...com, richard@....at, bbrezillon@...nel.org,
kdasu.kdev@...il.com, JaimeLiao <jaimeliao.tw@...il.com>,
Adam Borowski <kilobyte@...band.pl>
Subject: Re: [PATCH v4 1/4] mtd: rawnand: Add destructive operation
Hi Miquèl,
Can you please have a look at this update?
This patch has not received any change requests after two weeks but
let me know if you see anything that should be fixed.
Thanks!
-Dave
On Wed, Oct 25, 2023 at 5:25 PM William Zhang
<william.zhang@...adcom.com> wrote:
>
>
>
> On 10/23/2023 10:14 AM, dregan@...adcom.com wrote:
> > From: Boris Brezillon <bbrezillon@...nel.org>
> >
> > Erase and program operations need the write protect (wp) pin to be
> > de-asserted to take effect. Add the concept of destructive
> > operation and pass the information to exec_op() so controllers know
> > when they should de-assert this pin without having to decode
> > the command opcode.
> >
> > Signed-off-by: Boris Brezillon <bbrezillon@...nel.org>
> > Signed-off-by: David Regan <dregan@...adcom.com>
> > ---
> > Changes in v4: none
> >
> > Changes in v3: updated comments and email address
> >
> > Changes in v2: gave credit to Boris Brezillon
> > ---
> > drivers/mtd/nand/raw/nand_base.c | 6 ++++--
> > include/linux/mtd/rawnand.h | 9 +++++++++
> > 2 files changed, 13 insertions(+), 2 deletions(-)
> >
>
> Reviewed-by: William Zhang <william.zhang@...adcom.com>
Powered by blists - more mailing lists