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

Hi, Sorry for the delay but I'm waiting for 4.7-rc1 before taking new NAND patches, and decided to use this time to work on other stuff. On Wed, 18 May 2016 17:10:01 -0500 Kyle Roeschley wrote: > If erasing or writing the BBT fails, we should mark the current BBT > block

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

Hi, Sorry for the delay but I'm waiting for 4.7-rc1 before taking new NAND patches, and decided to use this time to work on other stuff. On Wed, 18 May 2016 17:10:01 -0500 Kyle Roeschley wrote: > If erasing or writing the BBT fails, we should mark the current BBT > block as bad and use the BBT

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

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

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

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: