Tony, [snip] >> So after the cleanup patch introducing CONFIG_SOC_OMAP4PLUS >> it can be changed as >> #ifdef (CONFIG_SOC_OMAP4PLUS) && !(defined(CONFIG_ARCH_OMAP2) || >> defined(CONFIG_ARCH_OMAP3)) >> >> So this will avoid patching this for the future socs. ? > > Well it seems that we've come to a conclusion that if we introduce > new config options, they should be based on features instead. So > CONFIG_SOC_HAS_OMAPXYZ_BLAH rather than CONFIG_SOC_OMAP4PLUS. > Sure thanks for clarifying. Then i will introduce a relevant config in my cleanup patch first and then add OMAP5. Thanks, Sricharan -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
