summaryrefslogtreecommitdiff
path: root/drivers/mtd/Kconfig
diff options
context:
space:
mode:
authorYang Ruirui <ruirui.r.yang@tieto.com>2011-03-14 09:50:56 +0800
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-03-25 17:04:18 +0200
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
The driver provides wear leveling by storing erase counter into the
OOB.
-config MTD_SWAP_STRICT
- bool "Strict erase error handling"
- depends on MTD_SWAP
- help
- Enables strict tolerance on failed erasures, marking erase blocks bad
- right after the first failed operation. With non-strict mode the
- erase operation is retried.
-
source "drivers/mtd/chips/Kconfig"
source "drivers/mtd/maps/Kconfig"