boris.brezillon at free-electrons.com
Sat May 20 01:48:04 PDT 2017
Not sure how you created this patchset, but you miss a Subject, and the
git format-patch -o <output-dir> -3 --cover-letter
to generate patches, then fill the cover letter in.
Once your cover letter is ready, you can send the patches with
git send-email --to ... --cc ... <output-dir>/*.patch
Le Fri, 19 May 2017 18:37:28 -0300,
"Mario J. Rugiero" <mrugiero at gmail.com> a écrit :
> Some manufacturers use different layouts than MTD for the NAND, creating
> incompatibilities when going from a vendor-specific kernel to mainline.
> In particular, NAND devices for AllWinner boards write non-FF values to
> the bad block marker, and thus false positives arise when detecting bad
> blocks with the MTD driver. Sometimes there are enough false positives
> to make the device unusable.
> A proposed solution is NAND scrubbing, something a user who knows what
> she's doing (TM) could do to avoid this. It consists in erasing blocks
> disregarding the BBM. Since the user must know what she's doing, the
> only way to enable this feature is through a per-chip debugfs entry.
More information about the linux-mtd