From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: kbuild devel list <linux-kbuild@vger.kernel.org>
Subject: Re: "header-y" versus "unifdef-y"?
Date: Wed, 22 Jul 2009 14:32:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0907221432240.27475@localhost> (raw)
In-Reply-To: <20090722183004.GA8457@merkur.ravnborg.org>
On Wed, 22 Jul 2009, Sam Ravnborg wrote:
> On Wed, Jul 22, 2009 at 08:25:03AM -0400, Robert P. J. Day wrote:
> >
> > is it my imagination, or did someone recently propose that there
> > will soon be no distinction between those two Kbuild directives since
> > it's just as easy to "unifdef" all of them, no matter what? has that
> > patch already been submitted for the next major release?
>
> Documentation/kbuild/makefiles.txt:
>
> --- 7.4 unifdef-y (deprecated)
>
> unifdef-y is deprecated. A direct replacement is header-y.
>
>
> That should answer your Q.
ah, quite right, thanks. i remembered someone saying that would
happen eventually, i didn't realize it had *already* happened.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
prev parent reply other threads:[~2009-07-22 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 12:25 "header-y" versus "unifdef-y"? Robert P. J. Day
2009-07-22 18:30 ` Sam Ravnborg
2009-07-22 18:32 ` Robert P. J. Day [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=alpine.LFD.2.00.0907221432240.27475@localhost \
--to=rpjday@crashcourse.ca \
--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 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.