public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: updated list of "unused" CONFIG variables now online
Date: Mon, 28 Dec 2009 06:06:17 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0912280602360.13623@localhost> (raw)


  based on this morning's "git pull", i've updated the list of
tree-wide CONFIG variables that are defined in a Kconfig file
somewhere but don't appear to be tested:

http://www.crashcourse.ca/wiki/index.php/Unused_CONFIG_variables

  a note:  some of those variables are starting to look depressingly
familiar as they've been around for *years*.  in many cases, they
don't hurt as they simply have no value if they're defined but not
tested.

  on the other hand, that list is a good way to identify typoes, as in
this example:

  ===== USB_ETH_EEM
  drivers/usb/gadget/Kconfig:681:config USB_ETH_EEM
  drivers/usb/gadget/ether.c:262:#ifdef USB_ETH_EEM

that's clearly a typo since the #ifdef should be using a "CONFIG_"
prefix -- that's the sort of thing that's flagged at that page.

  it's all broken down by top-level directory and subdirectory so pick
a subdirectory and see if anything looks odd or removable.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

                 reply	other threads:[~2009-12-28 11:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.00.0912280602360.13623@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox