On Sat, Jul 21, 2007 at 09:42:48AM +0200, Andi Kleen wrote:
> On Saturday 21 July 2007 09:35:33 Adrian Bunk wrote:
>
> > The problem with the current "merging" is that it's extremely hard to
> > figure out whether some code in x86_64 might be using some code in i386
> > since there are currently 5 (five) different mechanisms used for sharing
> > code between the two architectures.
> >
> > It happens so often that someone accidentally breaks one architecture
> > because he didn't notice the code also gets used on the other
> > architecture.
>
> That's not changing at all. Especially with even more sharing, (than I think
> would be prudent) like Thomas treated, you'll likely have to test compile both
> for most changes.
It's not about compilation, it's about seeing that this code might be
shared.
When e.g. changing a file under arch/i386/kernel/cpu/mtrr/ it's highly
surprising that this file might also be used on x86_64.
> -Andi
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]