[PATCH 0/4] char/misc: make some drivers more explicitly non-modular

[Paul Gortmaker]

In the previous merge window, we made changes to allow better
delineation between modular and non-modular code in commit
0fd972a7d91d6e15393c449492a04d94c0b89351 ("module: relocate module_init
from init.h to module.h").  This allows us to now ensure module code
looks modular and non-modular code does not accidentally look modular
without suffering build breakage.

Here we target code that is, by nature of their Kconfig settings, only
available to be built-in, but implicitly presenting itself as being
possibly modular by way of using modular headers, macros, and functions.

The goal here is to remove that illusion of modularity from these
drivers, but in a way that leaves the actual runtime unchanged.
In doing so, we remove code that has never been tested and adds
no value to the tree.  And we advance the process of expecting a
level of consistency between the Kconfig of a driver and the code
that the driver uses.

Build tested on and x86-64, and on ia64 for snsc.c after applying
to a baseline of char-misc/char-misc-next

Paul.
---

Cc: Arnd Bergmann <arnd@xxxxxxxx>
Cc: Clemens Ladisch <clemens@xxxxxxxxxx>
Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Cc: Jason Wessel <jason.wessel@xxxxxxxxxxxxx>
Cc: kgdb-bugreport@xxxxxxxxxxxxxxxxxxxxx

Paul Gortmaker (4):
  drivers/char: make efirtc.c driver explicitly non-modular
  drivers/char: make SGI snsc.c driver explicitly non-modular
  drivers/char: make hpet.c explicitly non-modular
  drivers/misc: make kgdbts.c slightly more explicitly non-modular

 drivers/char/efirtc.c | 13 +++----------
 drivers/char/hpet.c   | 25 +++----------------------
 drivers/char/snsc.c   |  5 ++---
 drivers/misc/kgdbts.c | 10 +++++-----
 4 files changed, 13 insertions(+), 40 deletions(-)

-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/