On Mon, Jun 16, 2014 at 9:17 AM, Tony Lindgren <t...@atomide.com> wrote: > * Tony Lindgren <t...@atomide.com> [140616 04:31]: >> * Arnd Bergmann <a...@arndb.de> [140616 04:18]: >> > >> > Let's see if others have similar opinions Rob's patch as a whole. >> > I'd still like to keep all the parts aside from the OMAP change >> > and just back out the change that caused the problems. >> > >> > Does that seem reasonable to you? >> >> Yes makes sense to me if others don't have similar issues. I guess >> it should be possible to verify that by diffing the generated >> .config files compared to the old ones.
Other than exynos (which is new to MP) and OMAP, the rest are straightforward user config to menuconfig conversions. > If you update Rob's patch and undo the omap2+ changes, you might > want to fold in something like the following to hide the omap > options behind a menu. This or reverting the OMAP part seems like the best change for now. > So far I have not come up with no great ideas on fixing this > properly short of requiring all omap .config files to add > CONFIG_ARCH_OMAP=y manually. Anybody got good ideas for that? I've failed to come up with anything... Rob > > Regards, > > Tony > > --- a/arch/arm/mach-omap2/Kconfig > +++ b/arch/arm/mach-omap2/Kconfig > @@ -1,3 +1,5 @@ > +menu "TI OMAP/AM/DM/DRA Family" > + > config ARCH_OMAP > bool > > @@ -342,3 +344,5 @@ config OMAP4_ERRATA_I688 > endmenu > > endif > + > +endmenu -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
