aboutsummaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorKrzysztof Halasa <khc@pm.waw.pl>2009-11-15 13:14:07 -0500
committerJiri Kosina <jkosina@suse.cz>2009-12-04 09:39:57 -0500
commit86185af927bebbb094f686ce5e3c908c7a418f4c (patch)
treecef28dfee09956e98618d2f207e83bfc3497cfd5 /drivers
parentbebd04cc4569844effbdae49c01a48e57fa77864 (diff)
mtd: Fix comment in Kconfig
IXDP425 and Coyote aren't based on IXP2000 but on IXP425. Signed-off-by: Krzysztof Halasa <khc@pm.waw.pl> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/mtd/maps/Kconfig6
1 files changed, 3 insertions, 3 deletions
diff --git a/drivers/mtd/maps/Kconfig b/drivers/mtd/maps/Kconfig
index faf482f101ee..847e214ade59 100644
--- a/drivers/mtd/maps/Kconfig
+++ b/drivers/mtd/maps/Kconfig
@@ -387,9 +387,9 @@ config MTD_IXP2000
387 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 387 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
388 help 388 help
389 This enables MTD access to flash devices on platforms based 389 This enables MTD access to flash devices on platforms based
390 on Intel's IXP2000 family of network processors such as the 390 on Intel's IXP2000 family of network processors. If you have an
391 IXDP425 and Coyote. If you have an IXP2000 based board and 391 IXP2000 based board and would like to use the flash chips on it,
392 would like to use the flash chips on it, say 'Y'. 392 say 'Y'.
393 393
394config MTD_FORTUNET 394config MTD_FORTUNET
395 tristate "CFI Flash device mapped on the FortuNet board" 395 tristate "CFI Flash device mapped on the FortuNet board"