I usually don't venture into the arch/ directories, as I can test
only on Intel and it's too easy to accidentally break other
architectures. I did take a quick look at the sys_sparc32 code, and
it seems to be very similar to the mainstream code. Perhaps some of
the routines don't need to have an arch/ version?
Yes, they can be shared.
And don't worry about "accidently" breaking other architectures. If
you do the changes and make a once over on them, this saves the port
maintainer the initial set of work. He's just as liable as you to
make mistakes in the changes.
Believe me, most of us port maintainers would rather fix up blemishes
and small thinkos in the work you do for us than do the entire thing
ourselves ;-) And also, when you do the work, you show your
intentions clearly to the port maintainer.
Later,
David S. Miller
davem@dm.cobaltmicro.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu