All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Peter Pan <peterpansjtu@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
	linux-mtd@lists.infradead.org,
	David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	linux-kernel@vger.kernel.org,
	"peterpandong@micron.com" <peterpandong@micron.com>
Subject: Re: [PATCH v2 0/7] mtd: nand: Abstract away the NAND interface type
Date: Thu, 17 Nov 2016 08:56:03 +0100	[thread overview]
Message-ID: <20161117085603.3f568599@bbrezillon> (raw)
In-Reply-To: <CAAyFORJYaNysioJDfjPyYKx0Eh4yvgrM3GHz8e=4J1Pcdc5-Eg@mail.gmail.com>

Hi Peter,

On Thu, 17 Nov 2016 14:26:37 +0800
Peter Pan <peterpansjtu@gmail.com> wrote:

> Hi Boris,
> 
> On Sun, Oct 16, 2016 at 10:35 PM, Boris Brezillon
> <boris.brezillon@free-electrons.com> wrote:
> > Hi,
> >
> > This series is aiming at providing a generic NAND layer to share code
> > between different NAND based devices.
> >
> > We currently have 3 different interfaces to interact with NANDs:
> > - Raw NANDs
> > - OneNANDs
> > - SPI NANDs
> >
> > Apart from the way these NAND devices are accessed they have a lot
> > in common, like the way the memory is organized, or their constraints.
> > This is usually a good sign that some work should be done to factorize
> > the code.
> >
> > This work has been started by Peter who wanted to re-use the BBT
> > code for its SPI-NAND driver. But I think we can push it further
> > other stuff (the software ECC implementation, or the way offsets are
> > converted to block/page number).
> >
> > Peter, can you please review/test this version, and if possible, post
> > the code you've done to support SPI NANDs.
> >  
> 
> I already finished review and test work. The BBT works well after I applied
> my modification which I already sent to your by email. I tried to build a new
> BBT on a new NAND and then mark one block to bad. Both works well.
> My test platform is Xilinx Zed board.

Thanks a lot for testing and reviewing this series. I'll address your
comments and send a new version soon.

My plan is to have it in -next just after 4.10-rc1 is released, in order
to detect bugs early.

> 
> I will try to rebase my SPI NAND patch on your patch and send it out.
> It will take me some time because I'm quite busy with other company affairs.

I'd be happy to review this part.

Regards,

Boris

  reply	other threads:[~2016-11-17  7:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16 14:35 [PATCH v2 0/7] mtd: nand: Abstract away the NAND interface type Boris Brezillon
2016-10-16 14:35 ` [PATCH v2 1/7] mtd: nand: Rename nand.h into rawnand.h Boris Brezillon
2016-10-16 14:35 ` [PATCH v2 2/7] mtd: nand: move raw NAND related code to the raw/ subdir Boris Brezillon
2016-10-16 14:35 ` [PATCH v2 3/7] mtd: nand: add a nand.h file to expose basic NAND stuff Boris Brezillon
2016-11-17  6:14   ` Peter Pan
2016-11-17  7:52     ` Boris Brezillon
2016-10-16 14:35 ` [PATCH v2 4/7] mtd: nand: raw: prefix conflicting names with nandc instead of nand Boris Brezillon
2016-10-16 14:35 ` [PATCH v2 5/7] mtd: nand: raw: create struct rawnand_device Boris Brezillon
2016-10-16 14:35 ` [PATCH v2 6/7] mtd: nand: raw: make BBT code more generic Boris Brezillon
2016-11-16  8:43   ` Peter Pan
2016-11-16  8:46     ` Boris Brezillon
2016-11-17  6:19   ` Peter Pan
2016-11-17  7:51     ` Boris Brezillon
2016-10-16 14:35 ` [PATCH v2 7/7] mtd: nand: move BBT code to drivers/mtd/nand/ Boris Brezillon
2016-11-17  6:26 ` [PATCH v2 0/7] mtd: nand: Abstract away the NAND interface type Peter Pan
2016-11-17  7:56   ` Boris Brezillon [this message]
2016-11-17  8:08     ` Peter Pan

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=20161117085603.3f568599@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=peterpandong@micron.com \
    --cc=peterpansjtu@gmail.com \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.