mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
	kbuild devel <kbuild-devel@lists.sourceforge.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: kbuild update
Date: Sun, 16 Sep 2007 22:38:48 +0200	[thread overview]
Message-ID: <20070916203848.GA10365@uranus.ravnborg.org> (raw)
In-Reply-To: <20070916122343.59e8885d.akpm@linux-foundation.org>

On Sun, Sep 16, 2007 at 12:23:43PM -0700, Andrew Morton wrote:
> On Sun, 16 Sep 2007 08:58:03 -0400 (EDT) "Robert P. J. Day" <rpjday@mindspring.com> wrote:
> 
> > On Sun, 16 Sep 2007, Sam Ravnborg wrote:
> > 
> > > A summary of what is planned to be submitted in next merge window for kbuild.
> > > The shortlog below have additional details but the headlines are:
> > ...
> > > o add script to find unused kconfig symbols (try it!)
> > 
> > based on my experiences with this, unless you filter carefully, you're
> > going to end up with a *whack* of false positives given the number of
> > developers who elect to name their local macros starting with a prefix
> > of "CONFIG_".  good luck dealing with *that*.  :-)
> 
> box:/usr/src/linux-2.6.23-rc6> grep -r '^[      ]*#[    ]*define[       ]*CONFIG_' . | wc -l
> 415
> 
> bah.  They're all bugs - The CONFIG_foo namespace is (should be) reserved in
> kernel coding.

I get (after a bit more filtering 349 hits of which 182 are outside drivers/

Of the 182 the 25 of them are in arch specific code.

I se no good reasons to address this unless we touch code in that area anyway.
But avoiding new entries are good.

	Sam


  reply	other threads:[~2007-09-16 20:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16  9:47 Sam Ravnborg
2007-09-16 12:58 ` Robert P. J. Day
2007-09-16 15:13   ` Sam Ravnborg
2007-09-16 15:21     ` Robert P. J. Day
2007-09-16 19:23   ` Andrew Morton
2007-09-16 20:38     ` Sam Ravnborg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-03 21:32 Kbuild update Sam Ravnborg
2008-01-03 21:46 ` Josh Boyer
2008-01-03 22:33 ` Jan Engelhardt
2008-01-04 19:43   ` Sam Ravnborg
2008-01-04 20:09     ` Jan Engelhardt
2008-01-04 13:23 ` WANG Cong
2008-01-04 14:39   ` Sam Ravnborg
2008-01-05  5:48     ` Adrian Bunk
2008-01-06 14:26       ` WANG Cong
2008-01-06 15:07         ` Adrian Bunk
2008-01-06 15:45           ` Sam Ravnborg
2008-01-09  2:32             ` WANG Cong
2008-01-09  5:18               ` Sam Ravnborg
2008-01-09  2:28           ` WANG Cong
2007-06-03 20:36 kbuild update Sam Ravnborg
2007-06-03 20:51 ` Sam Ravnborg

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=20070916203848.GA10365@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    /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

Powered by JetHome