mtd: fix Kconfig comment about 'armflash'

Message ID 20090223163050.7736.3796.stgit@Programuotojas
State Accepted
Commit 0b1b51f50ed7b4225d0631140de8873fb235a6c0
Headers show

Commit Message

Paulius Zaleckas Feb. 23, 2009, 4:30 p.m.
The real 'armflash' map driver is selected by CONFIG_MTD_ARM_INTEGRATOR

Signed-off-by: Paulius Zaleckas <>

 drivers/mtd/Kconfig |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)


diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index 7d04fb9..b8e35a0 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"