On Tue, Dec 01, 2009 at 04:08:19PM -0800, Tony Lindgren wrote: > Hi, > > * Olof Johansson <olof@xxxxxxxxx> [091201 12:06]: > > Having one combined defconfig that is the superset of the individual > > defconfigs for OMAP3 platforms is useful for easily finding build > > errors. Not to mention convenient as a base if you want to boot several > > platforms with a single kernel image. > > Good idea, that's what many people are already doing. Yeah, we're doing it internally for the boards we use for early software work. In PPC land we had good success booting a wide variety (even cross brands) with single kernels, but ARM isn't quite there yet :) > > Tony, I noticed linux-next doesn't build many of the OMAP defconfigs, > > and a handful of them won't build to date. I suggest adding this config, > > and I'll as Stephen Rothwell to add it as one of the configs that are > > tested (and build errors reported) for every release. > > > > He's reluctant to add too many individual configs since it adds time to > > each cycle, but one more can surely be acceptable. > > I've built tested the for-next patches, they compile just fine > except for the omap36xx patches which depend on an update to the > mach-types. Yep, I noticed that and figured it's no big deal and will happen when Russell pushes that update. > If you find some other omap related compile errors in for-next, > can you please post the errors to this list? Of course. The build errors I am referring to in this case are not in your for-next branch when built individually though, but instad when I built linux-next which included your branch and other work. I.e. others broke the omap compiles. Having a generic config that Stephen Rothwell can build before he pushes out a new release means others will be notified that they broke OMAP, which will benefit everyone in the long run. He could of course build individual ones but every added config adds to the turnaround time for him so he prefers just one or two. Thus the superset config I'm proposing. :) -Olof -- 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
