That doesn't explain why the sparc64 code went into the kernel in the first
place, rather than being put in with the rest of the iBCS code. If it hadn't
been separated from the original code, it wouldn't be getting out of sync at
all.
> ... I'd be happy for someone else to backport the
> sparc64 work to sparc32, but it seems I'm the only one who cares who
> actually intends to work on the code.
Except me - I've been working on the Solaris/x86 code. Should that be put into
arch/i386/solaris to mirror the Sparc64 version, or can we attempt to
reconcile them all in the iBCS code where they started off?
---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
-
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/