aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/mtd
diff options
context:
space:
mode:
authorMatt LaPlante <kernel1@cyberdogtech.com>2006-10-03 16:31:37 -0400
committerAdrian Bunk <bunk@stusta.de>2006-10-03 16:31:37 -0400
commit095096038d637c477ef3c1b674612bcbc4d60c2d (patch)
tree2e850ffb08e7c13756efe16c562022d1289e37e6 /drivers/mtd
parentc73a668c096fe3dd23c1062018e82eb85f5c7043 (diff)
Fix several typos in drivers/
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'drivers/mtd')
-rw-r--r--drivers/mtd/chips/Kconfig2
-rw-r--r--drivers/mtd/nand/Kconfig2
-rw-r--r--drivers/mtd/onenand/Kconfig2
3 files changed, 3 insertions, 3 deletions
diff --git a/drivers/mtd/chips/Kconfig b/drivers/mtd/chips/Kconfig
index 6d8f30deb868..72e6d73beb40 100644
--- a/drivers/mtd/chips/Kconfig
+++ b/drivers/mtd/chips/Kconfig
@@ -270,7 +270,7 @@ config MTD_JEDEC
270 tristate "JEDEC device support" 270 tristate "JEDEC device support"
271 depends on MTD && MTD_OBSOLETE_CHIPS && BROKEN 271 depends on MTD && MTD_OBSOLETE_CHIPS && BROKEN
272 help 272 help
273 Enable older older JEDEC flash interface devices for self 273 Enable older JEDEC flash interface devices for self
274 programming flash. It is commonly used in older AMD chips. It is 274 programming flash. It is commonly used in older AMD chips. It is
275 only called JEDEC because the JEDEC association 275 only called JEDEC because the JEDEC association
276 <http://www.jedec.org/> distributes the identification codes for the 276 <http://www.jedec.org/> distributes the identification codes for the
diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
index c99302ed3823..1831340e5f51 100644
--- a/drivers/mtd/nand/Kconfig
+++ b/drivers/mtd/nand/Kconfig
@@ -21,7 +21,7 @@ config MTD_NAND_VERIFY_WRITE
21 NAND flash device internally checks only bits transitioning 21 NAND flash device internally checks only bits transitioning
22 from 1 to 0. There is a rare possibility that even though the 22 from 1 to 0. There is a rare possibility that even though the
23 device thinks the write was successful, a bit could have been 23 device thinks the write was successful, a bit could have been
24 flipped accidentaly due to device wear or something else. 24 flipped accidentally due to device wear or something else.
25 25
26config MTD_NAND_ECC_SMC 26config MTD_NAND_ECC_SMC
27 bool "NAND ECC Smart Media byte order" 27 bool "NAND ECC Smart Media byte order"
diff --git a/drivers/mtd/onenand/Kconfig b/drivers/mtd/onenand/Kconfig
index 465961b8bcd1..373bddce8f1c 100644
--- a/drivers/mtd/onenand/Kconfig
+++ b/drivers/mtd/onenand/Kconfig
@@ -21,7 +21,7 @@ config MTD_ONENAND_VERIFY_WRITE
21 OneNAND flash device internally checks only bits transitioning 21 OneNAND flash device internally checks only bits transitioning
22 from 1 to 0. There is a rare possibility that even though the 22 from 1 to 0. There is a rare possibility that even though the
23 device thinks the write was successful, a bit could have been 23 device thinks the write was successful, a bit could have been
24 flipped accidentaly due to device wear or something else. 24 flipped accidentally due to device wear or something else.
25 25
26config MTD_ONENAND_GENERIC 26config MTD_ONENAND_GENERIC
27 tristate "OneNAND Flash device via platform device driver" 27 tristate "OneNAND Flash device via platform device driver"