From: Andrew Morton <akpm@linux-foundation.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Adrian Bunk <bunk@kernel.org>,
sam@ravnborg.org, "Robert P. J. Day" <rpjday@crashcourse.ca>,
kbuild devel list <linux-kbuild@vger.kernel.org>
Subject: Re: [2.6 patch] run all userspace headers through unifdef
Date: Thu, 22 May 2008 00:08:38 -0700 [thread overview]
Message-ID: <20080522000838.da3931e0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1211439612.21380.385.camel@pmac.infradead.org>
On Thu, 22 May 2008 08:00:12 +0100 David Woodhouse <dwmw2@infradead.org> wrote:
> On Wed, 2008-05-21 at 23:22 -0700, Andrew Morton wrote:
> >
> > This is going to be a bit of a pain for everyone - people are forever
> > patching those Kbuild files.
> >
> > Is there a way in which we can do this in stages? Treat header-y in
> > the same manner as unifdef-y, then get all the unifdef-y's switched over
> > to header-y and once that is done, remove the "treat header-y in the same
> > manner as unifdef-y" support?
>
> We could. But does that actually reduce the pain, or just spread it
> about a bit?
It means Stephen and I only need to carry the bulk of the patch for a
few days rather than a month or more.
next prev parent reply other threads:[~2008-05-22 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 0:18 [PATCH] KBUILD: Move non-__KERNEL__-checking headers to header-y Robert P. J. Day
2008-05-20 7:08 ` Andrew Morton
2008-05-21 8:36 ` Robert P. J. Day
2008-05-21 8:43 ` Andrew Morton
2008-05-21 9:00 ` David Woodhouse
2008-05-21 10:02 ` Adrian Bunk
2008-05-21 10:47 ` David Woodhouse
2008-05-21 17:41 ` [2.6 patch] run all userspace headers through unifdef Adrian Bunk
2008-05-22 6:22 ` Andrew Morton
2008-05-22 7:00 ` David Woodhouse
2008-05-22 7:08 ` Andrew Morton [this message]
2008-05-22 7:12 ` David Woodhouse
2008-05-22 7:28 ` Robert P. J. Day
2008-05-22 7:37 ` Adrian Bunk
2008-05-22 7:08 ` 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=20080522000838.da3931e0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.