aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/mtd/Kconfig
diff options
context:
space:
mode:
authorYang Ruirui <ruirui.r.yang@tieto.com>2011-03-13 21:50:56 -0400
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-03-25 11:04:18 -0400
commite21fa86ad0ffa2c292b104ea19bdaa46ceab7105 (patch)
tree9baf6f805b94d26196d001f883197843fde65cba /drivers/mtd/Kconfig
parentfc2ff592b5b41f3f32e790dd124eeb3bc80706c8 (diff)
mtdswap: kill strict error handling option
As Artem Bityutskiy suggested: this option is controversial, as we do not really have any prove it is useful. And it is too much to have it as a config parameter. So, better kill it and let the real mtdswap users decide whether it is needed or not. Signed-off-by: Yang Ruirui<ruirui.r.yang@tieto.com> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'drivers/mtd/Kconfig')
-rw-r--r--drivers/mtd/Kconfig8
1 files changed, 0 insertions, 8 deletions
diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index 5fe01d556657..b4567c35a322 100644
--- a/drivers/mtd/Kconfig
+++ b/drivers/mtd/Kconfig
@@ -335,14 +335,6 @@ config MTD_SWAP
335 The driver provides wear leveling by storing erase counter into the 335 The driver provides wear leveling by storing erase counter into the
336 OOB. 336 OOB.
337 337
338config MTD_SWAP_STRICT
339 bool "Strict erase error handling"
340 depends on MTD_SWAP
341 help
342 Enables strict tolerance on failed erasures, marking erase blocks bad
343 right after the first failed operation. With non-strict mode the
344 erase operation is retried.
345
346source "drivers/mtd/chips/Kconfig" 338source "drivers/mtd/chips/Kconfig"
347 339
348source "drivers/mtd/maps/Kconfig" 340source "drivers/mtd/maps/Kconfig"