From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: largest part of "badref" config variables now updated
Date: Mon, 28 Dec 2009 12:11:02 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912281204260.12924@localhost> (raw)
the lion's share of finding badref CONFIG variables is now done,
these two subpages:
http://www.crashcourse.ca/wiki/index.php/Badref_CONFIG_variables#arch.2F
http://www.crashcourse.ca/wiki/index.php/Badref_CONFIG_variables#drivers.2F
the rest of this page:
http://www.crashcourse.ca/wiki/index.php/Badref_CONFIG_variables
will be updated later today. just to refresh memories, those wiki
pages identify variables that are being tested, but are not being
defined in any Kconfig file anywhere. here's an example:
drivers/input/serio/i8042-ppcio.h:55:#elif defined(CONFIG_SPRUCE)
so that header file is testing CONFIG_SPRUCE when there's no such
variable. another example:
drivers/ssb/main.c:497:#ifdef CONFIG_SSB_SDIO
(perhaps that should be testing CONFIG_SSB_SDIOHOST?)
you get the idea. and, yes, you really should take the time to
examine your favourite subsystem, because if you end up wasting hours
tracking down a bug, won't you feel silly once you realize it was
identified months ago and listed at my wiki page? :-)
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 17:11 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.0912281204260.12924@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