Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-05-04 Thread Kyle Roeschley
On Fri, Apr 29, 2016 at 09:16:31PM +0200, Boris Brezillon wrote: > On Fri, 29 Apr 2016 12:34:18 -0500 > Kyle Roeschley wrote: > > > Hi Boris, > > > > On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > > > +Peter, who's currently reworking the NAND BBT

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-05-04 Thread Kyle Roeschley
On Fri, Apr 29, 2016 at 09:16:31PM +0200, Boris Brezillon wrote: > On Fri, 29 Apr 2016 12:34:18 -0500 > Kyle Roeschley wrote: > > > Hi Boris, > > > > On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > > > +Peter, who's currently reworking the NAND BBT code. > > > > > > On Wed,

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-04-29 Thread Boris Brezillon
On Fri, 29 Apr 2016 12:34:18 -0500 Kyle Roeschley wrote: > Hi Boris, > > On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > > +Peter, who's currently reworking the NAND BBT code. > > > > On Wed, 30 Mar 2016 15:13:51 +0200 > > Boris Brezillon

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-04-29 Thread Boris Brezillon
On Fri, 29 Apr 2016 12:34:18 -0500 Kyle Roeschley wrote: > Hi Boris, > > On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > > +Peter, who's currently reworking the NAND BBT code. > > > > On Wed, 30 Mar 2016 15:13:51 +0200 > > Boris Brezillon wrote: > > > > > Hi Kyle, > > >

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-04-29 Thread Kyle Roeschley
Hi Boris, On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > +Peter, who's currently reworking the NAND BBT code. > > On Wed, 30 Mar 2016 15:13:51 +0200 > Boris Brezillon wrote: > > > Hi Kyle, > > > > On Fri, 25 Mar 2016 17:31:16 -0500 > >

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-04-29 Thread Kyle Roeschley
Hi Boris, On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > +Peter, who's currently reworking the NAND BBT code. > > On Wed, 30 Mar 2016 15:13:51 +0200 > Boris Brezillon wrote: > > > Hi Kyle, > > > > On Fri, 25 Mar 2016 17:31:16 -0500 > > Kyle Roeschley wrote: > > > > > If

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-03-30 Thread Boris Brezillon
+Peter, who's currently reworking the NAND BBT code. On Wed, 30 Mar 2016 15:13:51 +0200 Boris Brezillon wrote: > Hi Kyle, > > On Fri, 25 Mar 2016 17:31:16 -0500 > Kyle Roeschley wrote: > > > If erasing or writing the BBT fails, we

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-03-30 Thread Boris Brezillon
+Peter, who's currently reworking the NAND BBT code. On Wed, 30 Mar 2016 15:13:51 +0200 Boris Brezillon wrote: > Hi Kyle, > > On Fri, 25 Mar 2016 17:31:16 -0500 > Kyle Roeschley wrote: > > > If erasing or writing the BBT fails, we should mark the current BBT > > block as bad and use the BBT

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-03-30 Thread Boris Brezillon
Hi Kyle, On Fri, 25 Mar 2016 17:31:16 -0500 Kyle Roeschley wrote: > If erasing or writing the BBT fails, we should mark the current BBT > block as bad and use the BBT descriptor to scan for the next available > unused block in the BBT. We should only return a failure if

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-03-30 Thread Boris Brezillon
Hi Kyle, On Fri, 25 Mar 2016 17:31:16 -0500 Kyle Roeschley wrote: > If erasing or writing the BBT fails, we should mark the current BBT > block as bad and use the BBT descriptor to scan for the next available > unused block in the BBT. We should only return a failure if there isn't > any space

[PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-03-25 Thread Kyle Roeschley
If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Based on original code implemented by Jeff Westfahl

[PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

2016-03-25 Thread Kyle Roeschley
If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Based on original code implemented by Jeff Westfahl . Signed-off-by: