dead CONFIG variables in kernel Makefiles

From: Robert P. J. Day
Date: Mon Mar 26 2007 - 19:35:39 EST



the output from a short script i wrote, locating all CONFIG_
variables in makefiles that don't appear to exist in any Kconfig file
anywhere in the source tree.

first, from the drivers/ directory:

===== DRM_FFB =====
./drivers/char/drm/Makefile:obj-$(CONFIG_DRM_FFB) += ffb.o
===== INPUT_POWER =====
./drivers/input/Makefile:obj-$(CONFIG_INPUT_POWER) += power.o
===== IPATH_CORE =====
./drivers/Makefile:obj-$(CONFIG_IPATH_CORE) += infiniband/
===== L7200_KEYB =====
./drivers/acorn/char/Makefile:obj-$(CONFIG_L7200_KEYB) += defkeymap-l7200.o keyb_l7200.o
===== RADIO_MIROPCM20 =====
./drivers/media/radio/Makefile:obj-$(CONFIG_RADIO_MIROPCM20) += miropcm20.o
===== RADIO_MIROPCM20_RDS =====
./drivers/media/radio/Makefile:obj-$(CONFIG_RADIO_MIROPCM20_RDS) += miropcm20-rds.o
===== SCSI_FD_8xx =====
./drivers/scsi/Makefile:obj-$(CONFIG_SCSI_FD_8xx) += seagate.o
===== USB_EGALAX =====
./drivers/usb/input/Makefile:obj-$(CONFIG_USB_EGALAX) += touchkitusb.o
===== USB_ITMTOUCH =====
./drivers/usb/input/Makefile:obj-$(CONFIG_USB_ITMTOUCH) += itmtouch.o
===== USB_MTOUCH =====
./drivers/usb/Makefile:obj-$(CONFIG_USB_MTOUCH) += input/
./drivers/usb/input/Makefile:obj-$(CONFIG_USB_MTOUCH) += mtouchusb.o
===== USB_OHCI_AT91 =====
./drivers/usb/Makefile:obj-$(CONFIG_USB_OHCI_AT91) += host/
===== ZS =====
./drivers/tc/Makefile:obj-$(CONFIG_ZS) += zs.o

and from the fs/ directory:

===== NLS_ABC =====
./fs/nls/Makefile:obj-$(CONFIG_NLS_ABC) += nls_abc.o
===== NLS_ISO8859_10 =====
./fs/nls/Makefile:obj-$(CONFIG_NLS_ISO8859_10) += nls_iso8859-10.o

rday

--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
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/