* Adrian Bunk <[EMAIL PROTECTED]> wrote:
> What I want is that e.g. after fiddling with kernel headers I want an
> easy way of having much compile coverage. And my script that builds
> all defconfig's is trivial (although it takes a day to finish).
no, i think you misunderstood me. I do allyesconfig testing to make sure
the kernel is still generic enough on PC hardware - not to catch build
breakage.
What i do against build breakage is randconfig testing. That catches far
more build breakage than a few limited number of defconfigs would ever.
More defconfigs would just be a constant maintenance drag, they are
rather pointless on PC hardware anyway (we'd have to have at least a few
hundred of them for it to be meaningful as a "default config") and it
does not really solve the problem either.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
