public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Adrian Bunk <bunk@kernel.org>,
	sam@ravnborg.org,
	kbuild devel list <linux-kbuild@vger.kernel.org>
Subject: Re: [2.6 patch] run all userspace headers through unifdef
Date: Thu, 22 May 2008 03:28:15 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805220327190.7016@localhost.localdomain> (raw)
In-Reply-To: <1211440369.21380.395.camel@pmac.infradead.org>

On Thu, 22 May 2008, David Woodhouse wrote:

> On Thu, 2008-05-22 at 00:08 -0700, Andrew Morton wrote:
> > 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.
>
> OK, maybe that makes sense then. Linus can do the conversion with a
> simple sed invocation whenever we're ready.

awesome.  another one of my cleanup scripts i can throw away.  then
i'll be down to ... uh ... lots.  :-)

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

  reply	other threads:[~2008-05-22  7:28 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
2008-05-22  7:12                     ` David Woodhouse
2008-05-22  7:28                       ` Robert P. J. Day [this message]
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=alpine.LFD.1.10.0805220327190.7016@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox