From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bug in arch/x86/include/asm/boot.h [Was: next cleanup report: "bad" references to CONFIG variables]
Date: Thu, 25 Jun 2009 17:43:07 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0906251739360.23271@localhost> (raw)
In-Reply-To: <20090625192412.GA15823@uranus.ravnborg.org>
On Thu, 25 Jun 2009, Sam Ravnborg wrote:
> If you continue this then please filter the know false positives.
> For once start ignoring defconfigs.
point taken. back at the "badrefs" page:
http://www.crashcourse.ca/wiki/index.php/Badref_CONFIG_variables
i've cleaned up the "arch" categories by removing all matches to
defconfig files, which cuts down the output considerably.
the "drivers" section will be cleaned similarly shortly.
rday
p.s. i did notice another false positive when the only references to
a "config" directive is nothing but other "select" directives. i'll
fix that one of these days. but it's never going to be perfect. law
of diminishing returns and all that.
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-06-25 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 14:34 next cleanup report: "bad" references to CONFIG variables Robert P. J. Day
2009-06-25 19:24 ` Bug in arch/x86/include/asm/boot.h [Was: next cleanup report: "bad" references to CONFIG variables] Sam Ravnborg
2009-06-25 19:27 ` Robert P. J. Day
2009-06-25 20:44 ` Sam Ravnborg
2009-06-25 21:43 ` Robert P. J. Day [this message]
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.0906251739360.23271@localhost \
--to=rpjday@crashcourse.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.