On Fri, 12 Oct 2001 13:14:41 +0100,
David Woodhouse <dwmw2@infradead.org> wrote:
>kaos@ocs.com.au said:
>> I was going to do it that way. The problem is that it gives no
>> indication if the module has been checked or not. Adding
>> EXPORT_NO_SYMBOLS says that somebody has reviewed the module and
>> decided that exporting no symbols is the correct behaviour. It is the
>> difference between no maintainer and a maintained module.
>
>Just change the default to no exported symbols, and a single depmod pass
>will tell you what broke because it's no longer exporting symbols which are
>required by something else. There's no need to add the EXPORT_NO_SYMBOLS
>cruft all over the place.
Your approach is "make an incompatible change and see what breaks, then
scramble to fix it". My approach is "get ready for this change so we
can have a clean cutover". Also EXPORT_NO_SYMBOLS is the only way to
clean up 2.4 and 2.2 kernels, there is no option to make an
incompatible change to modutils there.
-
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/
This archive was generated by hypermail 2b29 : Mon Oct 15 2001 - 21:00:45 EST