by Anton Blanchar » Sun, 02 Mar 2003 22:20:08
From a ppc64 perspective Im happy for this to be done ASAP :)Quote:> Actually Andi asked me to do the work. Dave, is it okay with you? What
> about other maintainers?
Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
1. ioctl32 consolidation -- call for testing
Date: Fri, 28 Feb 2003 14:23:31 +0100
cmd probably could be u32 (since it is ioctl32 after all), but I doubt
it matters, as two following entries are pointers so it looks to me
like it is going to be lost by alignment, anyway.
These pointers can (and WERE!) 32-bit on sparc64, so we wouldn't
have the alignment problem there.
All kernel text on sparc64 (even in modules) occur in the lower
32-bits of the address apce.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
2. UMSHFS+
5. ioctl32 consolidation -- call for testing
6. Compaq ODT on none Compaq ??
7. ioctl32 cleanup -- sparc64 parts
8. Caldera Openlinux users of Ver 1.2.0
9. [2.5.66] ioctl32 breakage on x86_64
10. ioctl32 cleanup -- x86-64 version
11. ioctl32: kill code duplication (sparc64 tester wanted)
12. ioctl32 emulation: kill 600 duplicated COMPATIBLE_IOCTL()s
13. ioctl32 cleanup -- rest of architectures