Re: [RFC, Announce] Unified x86 architecture, arch/x86

[Arjan van de Ven]

> Besides radical file movements like this are bad anyways. They cause
> a big break in patchkits and forward/backwards porting that doesn't 
> really help anybody.

Sorry Andi but I strongly disagree with your disapproval of this.


for existing out of tree patches it's not a big break, it's one sed
script away (until consolidation happens).

For distro backports... well that's a distro problem; the distros get
paid to do that work by their customers. We really can't hold back
mainline progress for that....

Having one tree is a lot of progress; it means we (Intel and the rest of
the kernel community) only have to add features, bugfixes and quirks to
one place. It means testing is shared. It means feature sets are shared.

The only argument against is "but there are quirks in the old one that I
don't want to see".. well Thomas solves that by having a clean way to do
per 32/64 files for the few cases where it's needed.


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/