From: Benjamin LaHaise <bcrl@kvack.org>
To: Andrew Morton <akpm@osdl.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
Bastian Blank <bastian@waldi.eu.org>,
Arthur Othieno <apgo@patchbomb.org>,
Jean Delvare <khali@linux-fr.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [PATCH/RFC] remove duplicate #includes, take II
Date: Sun, 19 Feb 2006 18:47:13 -0500 [thread overview]
Message-ID: <20060219234713.GA3192@kvack.org> (raw)
In-Reply-To: <20060218145525.GA32618@MAIL.13thfloor.at>
On Sat, Feb 18, 2006 at 03:55:25PM +0100, Herbert Poetzl wrote:
> so if folks want to cherry pick and/or comment on
> the first two categories, please do so, I will
> collect all the feedback and produce a patch to
> get rid of the duplicates later ...
This sort of patch isn't as interesting as actually fixing the mess
known as include/linux/sched.h and include/linux/sched.h... Most places
in the kernel don't actually need the majority of sched.h, just a handful
of functions like set_task_state(). fs.h is another tangled web of
dependancies. I did some experimenting back in the 2.2 days and it was
possible to cut something like 10-20% off the kernel build time.
That said, it's a big job.
-ben
--
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here
and they've asked us to stop the party." Don't Email: <dont@kvack.org>.
prev parent reply other threads:[~2006-02-19 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 14:55 [PATCH/RFC] remove duplicate #includes, take II Herbert Poetzl
2006-02-18 14:57 ` [PATCH/RFC] remove duplicate #includes, take II, A Herbert Poetzl
2006-02-18 14:58 ` [PATCH/RFC] remove duplicate #includes, take II, part B Herbert Poetzl
2006-02-19 0:19 ` Russell King
2006-02-18 14:59 ` [PATCH/RFC] remove duplicate #includes, take II, part C Herbert Poetzl
2006-02-19 23:47 ` Benjamin LaHaise [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=20060219234713.GA3192@kvack.org \
--to=bcrl@kvack.org \
--cc=akpm@osdl.org \
--cc=apgo@patchbomb.org \
--cc=bastian@waldi.eu.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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