From: David Woodhouse <dwmw2@infradead.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: why so many unexported headers checking __KERNEL__?
Date: Wed, 26 Mar 2008 13:19:46 +0000 [thread overview]
Message-ID: <1206537586.9540.280.camel@pmac.infradead.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0803260913350.6316@localhost.localdomain>
On Wed, 2008-03-26 at 09:16 -0400, Robert P. J. Day wrote:
> well, since i already have the output from my script, i might toss
> together some per-directory patches to start removing some of that.
> this sounds more like a one-shot thing than adding permanent checking
> to the build process.
Makes sense.
Remember, one of our goals is to move towards having files which are
just _copied_ (header-y) instead of having these ifdefs. If, in your
travels, you see a way you can split headers up more sensibly to achieve
that, it would be good.
--
dwmw2
next prev parent reply other threads:[~2008-03-26 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 6:31 Robert P. J. Day
2008-03-26 12:08 ` David Woodhouse
2008-03-26 12:53 ` Robert P. J. Day
2008-03-26 13:10 ` David Woodhouse
2008-03-26 13:16 ` Robert P. J. Day
2008-03-26 13:19 ` David Woodhouse [this message]
2008-03-26 13:23 ` Robert P. J. Day
2008-03-26 13:37 ` Robert P. J. Day
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=1206537586.9540.280.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®