All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Josh Boyer <jwboyer@gmail.com>,
	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 12:58:23 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802131250120.25604@localhost.localdomain> (raw)
In-Reply-To: <20080213174636.GB12259@uranus.ravnborg.org>

On Wed, 13 Feb 2008, Sam Ravnborg wrote:

> On Wed, Feb 13, 2008 at 10:44:27AM -0500, Robert P. J. Day wrote:
> > 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
> >   $
>
> $ git grep 405EX | grep select
> arch/powerpc/platforms/40x/Kconfig:     select 405EX
> arch/powerpc/platforms/40x/Kconfig:     select 405EX
>
> So it is used.

ok, i see the flaw in my logic.  the Kconfig variable 405EX isn't
tested *directly* by anyone, it's simply used to further "select"
other variables, which my script doesn't take into account.

  config 405EX
        bool
        select IBM_NEW_EMAC_EMAC4
        select IBM_NEW_EMAC_RGMII

i don't think i'm quite ready to add that logic to a simple scanning
script.

oh, well.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

      reply	other threads:[~2008-02-13 17:58 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
2008-02-13 17:46         ` Sam Ravnborg
2008-02-13 17:58           ` 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.1.00.0802131250120.25604@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.