> > under the circumstances, is there *any* cleanup worth doing WRT to > this issue? because of the fact that module.h currently includes > moduleparam.h, developers have been able to get away with being > incredibly sloppy in their includes. It is wortwhile to make module.h independent of moduleparam.h. The MODULE_INFO stuff has nothing to do with module parameters. But keep the include so you do not break the > 500 drivers. Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
- From: "Robert P. J. Day" <[email protected]>
- Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
- References:
- [PATCH] Factor out common MODULE_INFO content from module*.h files.
- From: "Robert P. J. Day" <[email protected]>
- Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
- From: Sam Ravnborg <[email protected]>
- Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
- From: "Robert P. J. Day" <[email protected]>
- Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
- From: Sam Ravnborg <[email protected]>
- Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
- From: "Robert P. J. Day" <[email protected]>
- [PATCH] Factor out common MODULE_INFO content from module*.h files.
- Prev by Date: Re: [PATCH]serial: make early_uart to use early_prarm instead of console_initcall
- Next by Date: Re: [2.6.22-rc1-mm1] section mismatch.
- Previous by thread: Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
- Next by thread: Re: [PATCH] Factor out common MODULE_INFO content from module*.h files.
- Index(es):
 |