[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM6PR02MB4779307E32670683AE9F60D6AFC90@DM6PR02MB4779.namprd02.prod.outlook.com>
Date: Wed, 17 Jul 2019 05:33:35 +0000
From: Naga Sureshkumar Relli <nagasure@...inx.com>
To: Boris Brezillon <boris.brezillon@...labora.com>
CC: "miquel.raynal@...tlin.com" <miquel.raynal@...tlin.com>,
"bbrezillon@...nel.org" <bbrezillon@...nel.org>,
"richard@....at" <richard@....at>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"computersforpeace@...il.com" <computersforpeace@...il.com>,
"marek.vasut@...il.com" <marek.vasut@...il.com>,
"vigneshr@...com" <vigneshr@...com>,
"yamada.masahiro@...ionext.com" <yamada.masahiro@...ionext.com>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Michal Simek <michals@...inx.com>,
Srikanth Vemula <svemula@...inx.com>,
"nagasuresh12@...il.com" <nagasuresh12@...il.com>
Subject: RE: [LINUX PATCH v18 1/2] mtd: rawnand: nand_micron: Do not over
write driver's read_page()/write_page()
Hi Boris,
> -----Original Message-----
> From: Boris Brezillon <boris.brezillon@...labora.com>
> Sent: Tuesday, July 16, 2019 1:15 PM
> To: Naga Sureshkumar Relli <nagasure@...inx.com>
> Cc: miquel.raynal@...tlin.com; bbrezillon@...nel.org; richard@....at;
> dwmw2@...radead.org; computersforpeace@...il.com; marek.vasut@...il.com;
> vigneshr@...com; yamada.masahiro@...ionext.com; linux-mtd@...ts.infradead.org; linux-
> kernel@...r.kernel.org; Michal Simek <michals@...inx.com>; Srikanth Vemula
> <svemula@...inx.com>; nagasuresh12@...il.com
> Subject: Re: [LINUX PATCH v18 1/2] mtd: rawnand: nand_micron: Do not over write
> driver's read_page()/write_page()
>
> On Tue, 16 Jul 2019 09:31:37 +0200
> Boris Brezillon <boris.brezillon@...labora.com> wrote:
>
> > On Mon, 15 Jul 2019 23:30:51 -0600
> > Naga Sureshkumar Relli <naga.sureshkumar.relli@...inx.com> wrote:
> >
> > > Add check before assigning chip->ecc.read_page() and
> > > chip->ecc.write_page()
> > >
> > > Signed-off-by: Naga Sureshkumar Relli
> > > <naga.sureshkumar.relli@...inx.com>
> > > ---
> > > Changes in v18
> > > - None
> > > ---
> > > drivers/mtd/nand/raw/nand_micron.c | 7 +++++--
> > > 1 file changed, 5 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/mtd/nand/raw/nand_micron.c
> > > b/drivers/mtd/nand/raw/nand_micron.c
> > > index cbd4f09ac178..565f2696c747 100644
> > > --- a/drivers/mtd/nand/raw/nand_micron.c
> > > +++ b/drivers/mtd/nand/raw/nand_micron.c
> > > @@ -500,8 +500,11 @@ static int micron_nand_init(struct nand_chip *chip)
> > > chip->ecc.size = 512;
> > > chip->ecc.strength = chip->base.eccreq.strength;
> > > chip->ecc.algo = NAND_ECC_BCH;
> > > - chip->ecc.read_page = micron_nand_read_page_on_die_ecc;
> > > - chip->ecc.write_page = micron_nand_write_page_on_die_ecc;
> > > + if (!chip->ecc.read_page)
> > > + chip->ecc.read_page = micron_nand_read_page_on_die_ecc;
> > > +
> > > + if (!chip->ecc.write_page)
> > > + chip->ecc.write_page = micron_nand_write_page_on_die_ecc;
> > >
> >
> > Seriously?! I told you this was inappropriate and you keep sending
> > this patch. So let's make it clear:
> >
> > Nacked-by: Boris Brezillon <boris.brezillon@...labora.com>
> >
> > Fix your controller driver instead of adding hacks to the Micron logic!
>
> Not even going to review the other patch: if you have to do that, that means the driver is
> broken. On a side note, this patch series is still not threaded as it should be and it's a v18 for a
> damn NAND controller driver! Sorry but you reached the limit of my patience. Please find
> someone to help you with that task.
My intention is not to resend this 1/2 again. Sorry for that.
We already had some discussion on [v17 1/2], https://lkml.org/lkml/2019/6/26/430
And there we didn't conclude that raw_read()/writes().
So I thought that, will send updated driver along with this patch, then will get more information about
The issue on the latest driver review.
There is nothing like keep on sending this patch, As you people are experts in the driver review,
if this patch is a hack, then we will definitely fix that in controller driver. I will find a way to do that.
But in this flow of patch sending, if the work I did hurts you, then I am really sorry for that.
Will fix this issue in the controller driver and will send the updated one.
Could you please let me know if this is OK.
I will send the series as threaded one from next time onwards.
Thanks,
pcieNaga Sureshkumar Relli
Powered by blists - more mailing lists