wdt: clean up unused modular infrastructure
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | watchdog: rtd119x: drop unused module.h includedrivers/ | +0 | 1 reply | |
| 2/5 | watchdog: watchdog_core: make it explicitly non-modulardrivers/ | +1 | 5 replies | |
| 3/5 | watchdog: npcm: make it explicitly non-modulardrivers/ | +6 | 2 replies | |
| 4/5 | watchdog: intel_scu: make it explicitly non-modulardrivers/ | +0 | 1 reply | |
| 5/5 | watchdog: coh901327: make it explicitly non-modulardrivers/ | +4 | 2 replies |
Reviews trailers per patch
3 of 5 patches have a Reviewed-by or Acked-by.
| Patch | Linus Walleij | Guenter Roeck |
|---|---|---|
| 1/5 | R-b | |
| 2/5 | ||
| 3/5 | ||
| 4/5 | R-b | |
| 5/5 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] wdt: clean up unused modular infrastructure
People can embed modular includes and modular exit functions into code that never use any of it, and they won't get any errors or warnings.
Using modular infrastructure in non-modules might seem harmless, but some of the downfalls this leads to are:
(1) it is easy to accidentally write unused module_exit/remove code
(2) it can be misleading when reading the source, thinking a driver can be modular when the Makefile and/or Kconfig prohibit it
(3) an unused include of the module.h header file will in turn include nearly everything else; adding a lot to CPP overhead.
(4) it gets copied/replicated into other drivers and can spread.
As a data point for #3 above, an empty C file that just includes the module.h header generates over 750kB of CPP output. Repeating the same experiment with init.h and the result is less than 12kB; with export.h it is only about 1/2kB; with both it still is less than 12kB.
Here, In this series, we do what has been done for other subsystems, like, net, x86, mfd, iommu.... and audit for uses of modular infrastructure inside code that currently can't be built as a module.
As always, the option exists for driver authors to convert their code to tristate, if there is a valid use case for it to be so. But since I don't have the context for each driver to know if such a use case exists, I limit myself to simply removing the unused code in order to make the driver consistent with the Makefile/Kconfig settings that control it.
Paul.
---
Paul Gortmaker (5):
watchdog: rtd119x: drop unused module.h include
watchdog: watchdog_core: make it explicitly non-modular
watchdog: npcm: make it explicitly non-modular
watchdog: intel_scu: make it explicitly non-modular
watchdog: coh901327: make it explicitly non-modular
drivers/watchdog/coh901327_wdt.c | 24 ++++-------------------- drivers/watchdog/intel_scu_watchdog.c | 18 ------------------ drivers/watchdog/npcm_wdt.c | 13 ++++++------- drivers/watchdog/rtd119x_wdt.c | 1 - drivers/watchdog/watchdog_core.c | 15 +-------------- 5 files changed, 11 insertions(+), 60 deletions(-)
Signature · 1 line
2.7.4