From: David Woodhouse <dwmw2@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org
Subject: Re: RFC: cleaning up the in-kernel headers
Date: Fri, 14 Jul 2006 01:11:14 +0100 [thread overview]
Message-ID: <1152835875.31372.27.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20060711160639.GY13938@stusta.de>
On Tue, 2006-07-11 at 18:06 +0200, Adrian Bunk wrote:
> I'd like to cleanup the mess of the in-kernel headers, based on the
> following rules:
> - every header should #include everything it uses
> - remove unneeded #include's from headers
If you also fancy removing gratuitous instances of #ifdef __KERNEL__,
that might be useful...
$ for a in `grep -rl __KERNEL__ include` ; do DIR=`dirname $a` ;
NAME=`basename $a` ; grep -q $NAME $DIR/Kbuild 2>/dev/null || grep -q
$NAME include/asm-generic/Kbuild.asm || echo $DIR/$NAME ; done | wc -l
481
--
dwmw2
prev parent reply other threads:[~2006-07-14 0:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 16:06 Adrian Bunk
2006-07-11 16:28 ` David Woodhouse
2006-07-11 17:33 ` Christoph Hellwig
2006-07-11 19:34 ` Sam Ravnborg
2006-07-11 19:41 ` Sam Ravnborg
2006-07-11 20:41 ` Randy.Dunlap
2006-07-11 21:37 ` Jörn Engel
2006-07-11 22:01 ` H. Peter Anvin
2006-07-11 22:20 ` Jörn Engel
2006-07-11 22:39 ` Linus Torvalds
2006-07-11 22:40 ` Adrian Bunk
2006-07-11 21:04 ` David Woodhouse
2006-07-11 22:24 ` Adrian Bunk
2006-07-11 17:07 ` Dave Jones
2006-07-11 17:15 ` Joshua Hudson
2006-07-11 18:19 ` Dave Jones
2006-07-11 22:27 ` Adrian Bunk
2006-07-11 19:05 ` Russell King
2006-07-11 22:19 ` Adrian Bunk
2006-07-11 20:26 ` [PATCH] Fix broken kernel headers preventing ARM build Russell King
2006-07-13 19:05 ` RFC: cleaning up the in-kernel headers Christoph Lameter
2006-07-15 4:18 ` Steven Rostedt
2006-07-15 4:59 ` Christoph Lameter
2006-07-17 0:53 ` Steven Rostedt
2006-07-20 10:56 ` Adrian Bunk
2006-07-14 0:11 ` David Woodhouse [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=1152835875.31372.27.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®