May I just suggest doing a
kernel/compat32.c
and doing most everything there? I think we're better off that way, even
if it means that "do_nanosleep()" etc cannot be static.
Please not this, this will continue the current problem we have
wherein overhauls of things like VFS infrastructure don't propagate to
the compat syscall implementations.
Putting the compat stuff right next to the "normal" version has
several advantages, one of which is that it is kept in sync with
things almost automatically. You have no choice but to notice
it, it's right there.
This isn't a "oh well we have to export some things" issue, it's a
long term maintainence issue. It is the main reason we want to move
this into a common area rather than deep within the arch code.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/