* Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi Ingo, > > On Sun, 14 Sep 2008 14:43:20 +0200 Ingo Molnar <mingo@xxxxxxx> wrote: > > > > yes, i agree with that direction. But it's difficult: the non-x86 > > architectures do not get much testing in practice at the development > > stage so trivial build bugs like this get only found at the latest > > stage. That's not actually bad in itself - stuff that is not used does > > not matter nearly as much as stuff that does get used. > > Well, its not really that difficult, you just have to remember that x86 > is not the whole world [...] [ ... just used by 90%+ of our active testers/developers ;-) ... ] > [...] and touching generic code just might affect the other > architectures - especially when the code you are touching is using > stuff that is clearly implemented by the architectures. Posting stuff > like this to linux-arch usually gets some attention (my apologies if > you did so, I don't remember seeing it). hm, you seem to have a bias for powerpc, but you should realize that cross-building for 20+ architectures (i.e. increasing the testing overhead twenty-fold), to cover the remaining <10% of the test space is unreasonable: for many developers it's not just virtually impossible in practice but also often a serious waste of time. Most people who have ever tried to collect cross-compilers for _all_ architectures and managed to get them all to work, and then used them consistently for all their patches will agree with that. We want to push unreasonable work to those who depend on the result of that unreasonable work - i.e. users/developers of those platforms - not everyone else. We dont want to hinder the progress of Linux with blindly requiring all patches that happen to touch common .c or .h files to successfully build on 20+ odd architectures. ... anyway, no real arguments about this specific case, if a fix/report is available we'll integrate/fix the issue. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
