On Wed, Nov 06, 2013 at 10:15:04AM -0600, Rob Herring wrote: > Other maintainers disagree because it reduces build coverage.
What possible build coverage are we talking about when building highbank on x86, for example? And what does a build failure in that configuration tell you if it builds and boots fine on your hardware? > Having done some cross arch clean-up, I have to agree with that > position. Iterating builds over different arches is bad enough, but > iterating over all configs for each arch is a pain. So make highbank depend only on the arches for which it is supposed to work but not for *all* arches. Look at how the other edac drivers do it, x86 ones depend on X86, tile on tile, etc, etc. Why should highbank be special? > It would be nice to have a uniform policy here. Simple: drivers should be selectable/buildable only on the arches they're supposed to run on. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
