OMAP2: avoid descending into disabled framebuffer dirs
Rather than always add the omap2 dirs to the build list (and thus force everyone to generate a useless built-in.o), bind the dirs to their relevant kconfig symbol. Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
This commit is contained in:
parent
44538b4315
commit
0d548a277c
1 changed files with 2 additions and 2 deletions
|
@ -1,6 +1,6 @@
|
||||||
obj-$(CONFIG_OMAP2_VRAM) += vram.o
|
obj-$(CONFIG_OMAP2_VRAM) += vram.o
|
||||||
obj-$(CONFIG_OMAP2_VRFB) += vrfb.o
|
obj-$(CONFIG_OMAP2_VRFB) += vrfb.o
|
||||||
|
|
||||||
obj-y += dss/
|
obj-$(CONFIG_OMAP2_DSS) += dss/
|
||||||
obj-y += omapfb/
|
obj-$(CONFIG_FB_OMAP2) += omapfb/
|
||||||
obj-y += displays/
|
obj-y += displays/
|
||||||
|
|
Loading…
Reference in a new issue