aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/mtd/Kconfig
diff options
context:
space:
mode:
authorPaulius Zaleckas <paulius.zaleckas@teltonika.lt>2009-04-06 09:10:54 -0400
committerJiri Kosina <jkosina@suse.cz>2009-06-12 12:01:45 -0400
commit0b1b51f50ed7b4225d0631140de8873fb235a6c0 (patch)
tree7c931ac4e9d855447319dde39f32ef4d349673f6 /drivers/mtd/Kconfig
parentcf3f9130f48ed04f32a31cfad21f576d45b8788b (diff)
trivial: mtd: fix Kconfig comment about 'armflash'
The real 'armflash' map driver is selected by CONFIG_MTD_ARM_INTEGRATOR Signed-off-by: Paulius Zaleckas <paulius.zaleckas@teltonika.lt> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/mtd/Kconfig')
-rw-r--r--drivers/mtd/Kconfig3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index 7d04fb9ddcaa..b8e35a0b4d72 100644
--- a/drivers/mtd/Kconfig
+++ b/drivers/mtd/Kconfig
@@ -154,7 +154,8 @@ config MTD_AFS_PARTS
154 154
155 You will still need the parsing functions to be called by the driver 155 You will still need the parsing functions to be called by the driver
156 for your particular device. It won't happen automatically. The 156 for your particular device. It won't happen automatically. The
157 'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example. 157 'armflash' map driver (CONFIG_MTD_ARM_INTEGRATOR) does this, for
158 example.
158 159
159config MTD_OF_PARTS 160config MTD_OF_PARTS
160 tristate "Flash partition map based on OF description" 161 tristate "Flash partition map based on OF description"