From: Russell King <rmk@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test5: configcheck results
Date: Tue, 9 Sep 2003 10:04:12 +0100 [thread overview]
Message-ID: <20030909100412.A25143@flint.arm.linux.org.uk> (raw)
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.
This seems like a hell of a lot to fix. Would it not just be easier to
use the -imacros or -include and eliminate the "do we need to include
linux/config.h" question for ever?
--
Russell King (rmk@arm.linux.org.uk) http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
2.6 ARM Linux - http://www.arm.linux.org.uk/
2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next reply other threads:[~2003-09-09 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 9:04 Russell King [this message]
2003-09-09 19:40 ` 2.6.0-test5: configcheck results Sam Ravnborg
2003-09-09 20:06 ` Randy.Dunlap
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=20030909100412.A25143@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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