On Tue, 8 Feb 2011, Santosh Shilimkar wrote: > > I think it's probably going to be better to _purposely_ break the > > OMAP build when it covers v6 and v7 CPUs in these kernels as I don't > > think it's sanely fixable given where we are. Agreed. At least making SMP unavailable when both v6 and v7 are configured should be small and good enough for 2.6.38-rc5. > Any alternative possible other than breaking the omap2plus build? > It's quite useful to have one build which covers majority of the > omap machines. Just merge this patch series in your testing tree, or create two configs (two builds) instead of only (a broken) one. Or use linux-next for testing which would be even more beneficial. Nicolas -- 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
