mtd: nand: omap2: Rename shippable module to omap2_nand
authorRoger Quadros <rogerq@ti.com>
Fri, 21 Aug 2015 10:45:35 +0000 (13:45 +0300)
committerBrian Norris <computersforpeace@gmail.com>
Wed, 2 Sep 2015 21:04:49 +0000 (14:04 -0700)
As both omap2 onenand and omap2 nand driver modules are
named the same i.e. "omap2.ko", only one of them gets shipped
during MODPOST if both are configured as loadable modules.

To avoid this ambiguity let's ship the omap2 nand
driver as "omap2_nand.ko"

Reported by Pierre Neyron via github
https://github.com/beagleboard/linux/issues/40

Cc: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
drivers/mtd/nand/Makefile

index 1f897ec3c242a977a52128e37f56ef9431fbd548..075a027632b5c88ac73d2d1fd7eed49569f713c3 100644 (file)
@@ -26,7 +26,8 @@ obj-$(CONFIG_MTD_NAND_CS553X)         += cs553x_nand.o
 obj-$(CONFIG_MTD_NAND_NDFC)            += ndfc.o
 obj-$(CONFIG_MTD_NAND_ATMEL)           += atmel_nand.o
 obj-$(CONFIG_MTD_NAND_GPIO)            += gpio.o
-obj-$(CONFIG_MTD_NAND_OMAP2)           += omap2.o
+omap2_nand-objs := omap2.o
+obj-$(CONFIG_MTD_NAND_OMAP2)           += omap2_nand.o
 obj-$(CONFIG_MTD_NAND_OMAP_BCH_BUILD)  += omap_elm.o
 obj-$(CONFIG_MTD_NAND_CM_X270)         += cmx270_nand.o
 obj-$(CONFIG_MTD_NAND_PXA3xx)          += pxa3xx_nand.o