Re: [PATCH v2 02/12] mtd: nand_bbt: introduce struct nand_bbt

Brian, Peter, On Tue, 15 Dec 2015 05:59:28 + Peter Pan wrote: > From: Brian Norris > > Currently nand_bbt.c is tied with struct nand_chip, and it makes other > NAND family chips hard to use nand_bbt.c. Maybe it's the reason why > onenand has own bbt(onenand_bbt.c). > > Separate struct

Re: [PATCH v2 02/12] mtd: nand_bbt: introduce struct nand_bbt

Brian, Peter, On Tue, 15 Dec 2015 05:59:28 + Peter Pan wrote: > From: Brian Norris > > Currently nand_bbt.c is tied with struct nand_chip, and it makes other > NAND family chips hard to use nand_bbt.c. Maybe it's the reason why >

[PATCH v2 02/12] mtd: nand_bbt: introduce struct nand_bbt

From: Brian Norris Currently nand_bbt.c is tied with struct nand_chip, and it makes other NAND family chips hard to use nand_bbt.c. Maybe it's the reason why onenand has own bbt(onenand_bbt.c). Separate struct nand_chip from BBT code can make current BBT shareable. We create struct nand_bbt to

[PATCH v2 02/12] mtd: nand_bbt: introduce struct nand_bbt

From: Brian Norris Currently nand_bbt.c is tied with struct nand_chip, and it makes other NAND family chips hard to use nand_bbt.c. Maybe it's the reason why onenand has own bbt(onenand_bbt.c). Separate struct nand_chip from BBT code can make current BBT shareable.