From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: latest list of unused Kconfig variables
Date: Wed, 13 Feb 2008 10:44:27 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802131038130.30959@localhost.localdomain> (raw)
In-Reply-To: <20080213093314.3220e29d@zod.rchland.ibm.com>
On Wed, 13 Feb 2008, Josh Boyer wrote:
> OK. Well all of your hits for 405EX, 440GRX, 440SPe, and
> WANT_DEVICE_TREE in arch/powerpc seem bogus. I dunno if you prune
> those when reported or not.
not normally, but i don't know what you mean by "bogus":
$ grep -r "config 405EX" *
arch/powerpc/platforms/40x/Kconfig:config 405EX
$
$ grep -r CONFIG_405EX *
arch/powerpc/configs/makalu_defconfig:CONFIG_405EX=y
arch/powerpc/configs/kilauea_defconfig:CONFIG_405EX=y
$
so, AFAICT, there exists a definition of the Kconfig variable 405EX,
which is subsequently not referenced *anywhere* in the tree except in
a couple defconfig files, which don't count. how, then, does that
Kconfig variable have any practical value? or am i missing something
painfully obvious?
> > > And you have false positives on several CPU variables, as they
> > > are used within Kconfig files themselves to select different
> > > sets of options.
> >
> > yes, i know ... perhaps there's a simple way to filter those out
> > but, at the moment, it's pure brute force. i'm guessing i could
> > make that script a bit smarter but it probably isn't worth the
> > investment in time. law of diminishing returns and all that.
>
> Maybe. If the same false positives keep showing up people might
> ignore it. I won't, but others might.
fair enough, but since this scanning happens only once every release,
it's not like it's a burden. and if people want to ignore it, that's
fine, too.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
next prev parent reply other threads:[~2008-02-13 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 8:56 latest list of unused Kconfig variables Robert P. J. Day
2008-02-13 9:20 ` Paul Mundt
2008-02-13 9:26 ` Robert P. J. Day
2008-02-13 13:32 ` Josh Boyer
2008-02-13 15:07 ` Robert P. J. Day
2008-02-13 15:16 ` Sam Ravnborg
2008-02-13 15:32 ` Robert P. J. Day
2008-02-13 15:33 ` Josh Boyer
2008-02-13 15:44 ` Robert P. J. Day [this message]
2008-02-13 17:46 ` Sam Ravnborg
2008-02-13 17:58 ` 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.1.00.0802131038130.30959@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.