> 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" ? Sounds pretty dumb to me. Getting this in -next has to be a good thing given the fact you and James don't agree on it, because thats the one place any merge collisions can be fixed and the combined bleeding edge x86 and voyager mods can be seen together and refined. I don't think ignoring voyager is useful - separating it out more probably is. Not-quite-PC hardware is on the way back, and OLPC is just the beginning so we *need* the mechanisms to support such platforms. Alan -- 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
