mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test5: configcheck results
Date: Tue, 9 Sep 2003 13:06:50 -0700	[thread overview]
Message-ID: <20030909130650.0670778d.rddunlap@osdl.org> (raw)
In-Reply-To: <20030909194001.GB3009@mars.ravnborg.org>

On Tue, 9 Sep 2003 21:40:01 +0200 Sam Ravnborg <sam@ravnborg.org> wrote:

| On Tue, Sep 09, 2003 at 10:04:12AM +0100, Russell King wrote:
| > Hi all,
| > 
| > I just ran make configcheck on 2.6.0-test5 and the results are:
| > 
| >     832 files need linux/config.h but don't actually include it.
| >     689 files which include linux/config.h but don't require the header.
| 
| Randy, you have looked into related perl scripts. Is the result of
| checkconfig.pl reliable?

They aren't perfect.  I consider them more like 80-90% solutions.
Usable until there's a better solution IMO, like maybe sparse.

The perl scripts don't look at other #included files to check if they
supply any of the needed #defines.  I.e., they look only at the one
file being searched to check if it uses names (CONFIG_*) without
#include-ing config.h in this case, so it can produce false positives.

I looked quickly at crypto/tcrypt.c (which is listed as needing config.h).
It #includes linux/init.h, which #includes linux/config.h.
I expect that there are several...or many like this.

--
~Randy

  reply	other threads:[~2003-09-09 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09  9:04 Russell King
2003-09-09 19:40 ` Sam Ravnborg
2003-09-09 20:06   ` Randy.Dunlap [this message]
2003-09-10  0:22   ` Andries Brouwer
2003-09-09 22:01 ` bill davidsen

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=20030909130650.0670778d.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome