-Index: linux-2.6.24/drivers/mtd/Kconfig
+Index: linux-2.6.24.2/drivers/mtd/Kconfig
===================================================================
---- linux-2.6.24.orig/drivers/mtd/Kconfig
-+++ linux-2.6.24/drivers/mtd/Kconfig
+--- linux-2.6.24.2.orig/drivers/mtd/Kconfig
++++ linux-2.6.24.2/drivers/mtd/Kconfig
@@ -160,6 +160,22 @@ config MTD_AFS_PARTS
for your particular device. It won't happen automatically. The
'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
comment "User Modules And Translation Layers"
config MTD_CHAR
-Index: linux-2.6.24/drivers/mtd/Makefile
+Index: linux-2.6.24.2/drivers/mtd/Makefile
===================================================================
---- linux-2.6.24.orig/drivers/mtd/Makefile
-+++ linux-2.6.24/drivers/mtd/Makefile
+--- linux-2.6.24.2.orig/drivers/mtd/Makefile
++++ linux-2.6.24.2/drivers/mtd/Makefile
@@ -11,6 +11,7 @@ obj-$(CONFIG_MTD_CONCAT) += mtdconcat.o
obj-$(CONFIG_MTD_REDBOOT_PARTS) += redboot.o
obj-$(CONFIG_MTD_CMDLINE_PARTS) += cmdlinepart.o