finding unused Kconfig variables in the source tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


  as i mentioned in an earlier post, i threw together a quick script
that scans the source tree, not for dead CONFIG vars (those that are
checked but never defined in a Kconfig file) but for the exact
opposite -- those that are *defined* in a Kconfig file but are
apparently never used anywhere.

  for example (since the CRIS architecture came up recently), here's
the first few lines of output (the script is still running as we

$ ../ arch/cris
arch/cris/arch-v32/drivers/Kconfig:config ETRAX_ETHERNET_HW_CSUM
arch/cris/arch-v32/drivers/Kconfig:config ETRAX_ETHERNET_IFACE0

  that tells me that, unless i've completely screwed my programming, a
Kconfig file defines the variable ETRAX_ETHERNET_HW_CSUM, which is
subsequently never referenced by anything anywhere in the tree.
(that would normally suggest a feature that was removed from the tree
without removing its controlling CONFIG variable.)

  i'll run this on bits of the tree at a time and send the results to
the appropriate people, at which point they can do what they want in
terms of cleaning Kconfig files.


p.s.  perhaps one of the CRIS folks could verify that those variables
are, in fact, unused, so i know i haven't screwed something up

Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at
Please read the FAQ at

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux