All of lore.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: latest scan for "bad" config variable references in kernel tree
Date: Fri, 23 Jul 2010 10:45:10 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1007231040330.958@lynx> (raw)


  as of 2.6.35-rc6, i ran another scan of the tree, looking for "bad"
config variable references, as in, preprocessor tests of CONFIG_
variables that aren't defined in any Kconfig file that i can see.

  it's all broken down by directory and subdirectory:

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

  as an example, here's what showed up under drivers/mmc:

>>>>> MMC_EMBEDDED_SDIO
drivers/mmc/host/msm_sdcc.c:1148:#ifdef CONFIG_MMC_EMBEDDED_SDIO
>>>>> MMC_MSM7X00A_RESUME_IN_WQ
drivers/mmc/host/msm_sdcc.h:238:#ifdef CONFIG_MMC_MSM7X00A_RESUME_IN_WQ
drivers/mmc/host/msm_sdcc.c:1060:#ifdef CONFIG_MMC_MSM7X00A_RESUME_IN_WQ

  as in, there's a test for "CONFIG_MMC_EMBEDDED_SDIO" when there is
no definition of such a variable in a Kconfig file.

  more scanning coming later, but that page covers the whole tree
looking for just that property.

rday

-- 

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

        Top-notch, inexpensive online Linux/OSS/kernel courses
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

                 reply	other threads:[~2010-07-23 14:45 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.DEB.2.00.1007231040330.958@lynx \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.