From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: kbuild devel list <linux-kbuild@vger.kernel.org>
Subject: "header-y" versus "unifdef-y"?
Date: Wed, 22 Jul 2009 08:25:03 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0907220823370.19368@localhost> (raw)
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?
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
========================================================================
next reply other threads:[~2009-07-22 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 12:25 Robert P. J. Day [this message]
2009-07-22 18:30 ` "header-y" versus "unifdef-y"? Sam Ravnborg
2009-07-22 18:32 ` 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=alpine.LFD.2.00.0907220823370.19368@localhost \
--to=rpjday@crashcourse.ca \
--cc=linux-kbuild@vger.kernel.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