> From: Werner Almesberger [mailto:Werner.Almesberger@epfl.ch]
> Sent: Friday, December 15, 2000 1:21 PM
> I don't think restructuring the headers in this way would cause
> a long period of instability. The main problem seems to be to
> decide what is officially private and what isn't.
--- If someone wants to restructure headers, that's fine. I was only trying to understand the confusingly stated intentions of Linus. I was attempting to fit into those intentions, not change the world.> > Any other solution, as I see it, would break existing module code. > > Hmm, I think what I've outlined above wouldn't break more code than > your approach. Obviously, modiles currently using "private" interfaces > are in trouble either way. --- You've misunderstood. My approach would break *nothing*.
If module-public include file includes a private, it would still work since 'sys' would be a directory under 'include/linux'. No new links need be added, needed or referenced. Thus nothing breaks.
-l - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Dec 15 2000 - 21:00:33 EST