On Wed, 10 Jun 2009, Ingo Molnar wrote: > > * Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote: > > > > This code has been NAK-ed by the x86 maintainers: > > > > > > - Due to the absurd irrelevance of Voyager/x86/Linux hardware > > > > > > - Due to the thousands of lines of of code it adds to arch/x86 > > > to support a 486/P5 era piece of hardware > > > > > > - and due to its negative track record of: > > > > > > v2.6.27.0: Voyager was broken - it did not even build. (!) > > > v2.6.28.0: Voyager was broken - it did not even build. (!) > > > v2.6.29-rc5: Voyager was broken - it did not even build. (!) > > > > So Ingo you are arguing "It didn't work in some releases so we > > want to make it continue not to work by trying to keep the fixes > > out" ? > > No. This code is not in Linux right now, and that i see no reason to > put it back, for the (many) reasons outlined. Ingo, "absurd irrelevance" is not a reason. If it was, we'd lose about half our filesystems etc. Neither is "thousands of lines of code", or "it hasn't always worked". Again, if it was, then we'd have to get rid of just about all drivers out there. So give some real reasons. "It's a maintenance nightmare because it does xyz" might be a reason. But then we really need to see the "xyz" part too. Alan is definitely right that we're likely to see more of the "non-PC" platforms as x86 tries to do embedded. Linus -- 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
