I think it's worth the effort. Especially if IBM wants to keep the 32 (31)bit
port alife long-term. Having two codebases that are mostly the same doesn't
sound like a good idea for fix propagation to me.
> and changing all the documentation referring to arch/s390x?
How much documentation outside the kernel tree knows about it?
> We do indeed want to merge include/asm-s390 include/asm-s390x, which would
> help building a compiler that supports both on s390x,
I think it's a good idea but don't understand the compiler depency. Why
do you need asm-s390 and asm-s390x to be the same to have an compiler that
works for 32bit and 64bit mode? Today e.g. the sparc and x86 compilers
can support both modes with very different kernel headers.
I don't see how you want to make the s390x port refer to include/asm-s390
easily when ARCH is still s390x..
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/