I disagree with this, as
a) 2.1.125 does build on those architectures and does run (in UP)
b) till two or three days ago, neither sparc32/SMP, nor sparc64/SMP actually
worked even in vger CVS (nor compiled), so it does not matter if those two
SMP ports will be unstable for one or two more days.
c) if you tell me where is your current patch, I can test it on sparc32/SMP
and davem can test it on sparc64/SMP, but I don't expect any big problems
So everything is up to Linus. If i386 is stable with it even in 2.1.125,
then I'd strongly suggest considering that change to go in.
And for early 2.3 I'd strongly vote for dancing Makefiles or something like
that, it is horrible to maintain sparc32/UP, sparc32/SMP, sparc64/UP,
sparc64/SMP trees and ensure that any tiny change in some file common to
them does not hurt any of the four compiles. And doing always make mrproper
and start full compilation again is really unpleasant.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.125 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/