summaryrefslogtreecommitdiffstats
path: root/fs/autofs/init.c
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2007-01-31 11:38:53 +0200
committerDavid Woodhouse <dwmw2@infradead.org>2007-02-09 15:34:08 +0000
commita7a6ace1406f95c3edb8365788f85984377f3832 (patch)
tree852a51608c1e2f437786750ca326ee8ce4b61364 /fs/autofs/init.c
parent73a4421c5a0aa77b996891e7616b396c360b3ed8 (diff)
downloadop-kernel-dev-a7a6ace1406f95c3edb8365788f85984377f3832.zip
op-kernel-dev-a7a6ace1406f95c3edb8365788f85984377f3832.tar.gz
[JFFS2] Use MTD_OOB_AUTO to automatically place cleanmarker on NAND
Nowadays MTD supports an MTD_OOB_AUTO option which allows users to access free bytes in NAND's OOB as a contiguous buffer, although it may be highly discontinuous. This patch teaches JFFS2 to use this nice feature instead of the old MTD_OOB_PLACE option. This for example caused problems with OneNAND. Now JFFS2 does not care how are the free bytes situated. This may change position of the clean marker on some flashes, but this is not a problem. JFFS2 will just re-erase the empty eraseblocks and write the new (correct) clean marker. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Diffstat (limited to 'fs/autofs/init.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud