From: Paul Mundt <lethal@linux-sh.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Randy Dunlap <randy.dunlap@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: duplicated include files
Date: Mon, 5 Nov 2007 12:02:40 +0900 [thread overview]
Message-ID: <20071105030240.GA26439@linux-sh.org> (raw)
In-Reply-To: <20071104190348.GN12045@stusta.de>
On Sun, Nov 04, 2007 at 08:03:48PM +0100, Adrian Bunk wrote:
> BTW: "make includecheck" already does the same...
>
When was that added? It's not listed in the 'make help', and I see
there's a versioncheck too that's not reported. Some of these are
actually useful, I wonder what else is lurking in the depths of
undocumented Makefile target land ;-)
docs: Add includecheck/versioncheck to 'make help'
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
---
diff --git a/Makefile b/Makefile
index 188c3b6..1ab40ac 100644
--- a/Makefile
+++ b/Makefile
@@ -1168,6 +1168,8 @@ help:
@echo ''
@echo 'Static analysers'
@echo ' checkstack - Generate a list of stack hogs'
+ @echo ' versioncheck - Sanity check on version.h usage'
+ @echo ' includecheck - Sanity check on duplicate includes'
@echo ' namespacecheck - Name space analysis on compiled kernel'
@echo ' export_report - List the usages of all exported symbols'
@if [ -r $(srctree)/include/asm-$(SRCARCH)/Kbuild ]; then \
next prev parent reply other threads:[~2007-11-05 3:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 17:31 duplicated include files Robert P. J. Day
2007-11-04 18:07 ` Randy Dunlap
2007-11-04 18:37 ` Robert P. J. Day
2007-11-04 18:46 ` Randy Dunlap
2007-11-04 19:03 ` Adrian Bunk
2007-11-04 19:10 ` Robert P. J. Day
2007-11-05 3:02 ` Paul Mundt [this message]
2007-11-05 8:27 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2007-11-04 19:41 Marco Costalba
2007-11-04 19:43 ` Marco Costalba
2007-11-04 19:49 ` Robert P. J. Day
2007-11-04 23:20 ` Jeremy Fitzhardinge
2007-11-05 3:49 ` Robert P. J. Day
2007-11-04 23:43 ` Bernd Petrovitsch
2007-11-04 19:51 ` Randy Dunlap
2007-11-05 10:51 ` Geert Uytterhoeven
2007-11-05 11:38 ` Marco Costalba
2007-11-14 20:40 ` 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=20071105030240.GA26439@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rpjday@crashcourse.ca \
/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