From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Bug in arch/x86/include/asm/boot.h [Was: next cleanup report: "bad" references to CONFIG variables]
Date: Thu, 25 Jun 2009 15:27:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0906251521430.12376@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.
just to be clear, yes, there are numerous output lines from
defconfig files, but a simple entry in a defconfig file can never
*contribute* to something being flagged as bad or unused. all those
lines represent is the subsequent global search once something *has*
been flagged as unused or bad, just to show where it occurs anywhere
in the tree (which is sometimes informative).
if a variable occurred *only* in defconfig files, it would be
ignored and nothing would be printed for it. but if that defconfig
output has no value, i can toss it.
rday
--
========================================================================
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
========================================================================
next prev parent reply other threads:[~2009-06-25 19:29 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 [this message]
2009-06-25 20:44 ` Sam Ravnborg
2009-06-25 21:43 ` Robert P. J. Day
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.0906251521430.12376@localhost \
--to=rpjday@crashcourse.ca \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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.