Hi, * Olof Johansson <[email protected]> [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. <snip> > 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. If you find some other omap related compile errors in for-next, can you please post the errors to this list? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
