diff options
author | Paulius Zaleckas <paulius.zaleckas@teltonika.lt> | 2009-04-06 17:10:54 +0400 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2009-06-12 20:01:45 +0400 |
commit | 0b1b51f50ed7b4225d0631140de8873fb235a6c0 (patch) | |
tree | 7c931ac4e9d855447319dde39f32ef4d349673f6 /drivers | |
parent | cf3f9130f48ed04f32a31cfad21f576d45b8788b (diff) | |
download | linux-0b1b51f50ed7b4225d0631140de8873fb235a6c0.tar.xz |
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')
-rw-r--r-- | drivers/mtd/Kconfig | 3 |
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 You will still need the parsing functions to be called by the driver for your particular device. It won't happen automatically. The - 'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example. + 'armflash' map driver (CONFIG_MTD_ARM_INTEGRATOR) does this, for + example. config MTD_OF_PARTS tristate "Flash partition map based on OF description" |