From: Adrian Bunk <bunk@stusta.de>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] process include/linux/if_{addr,link}.h with unifdef
Date: Wed, 24 Jan 2007 11:20:44 +0100 [thread overview]
Message-ID: <20070124102044.GG17836@stusta.de> (raw)
In-Reply-To: <20070123.220517.115910657.davem@davemloft.net>
On Tue, Jan 23, 2007 at 10:05:17PM -0800, David Miller wrote:
> From: Adrian Bunk <bunk@stusta.de>
> Date: Sun, 21 Jan 2007 20:13:19 +0100
>
> > After commit d3dcc077bf88806201093f86325ec656e4dbfbce,
> > include/linux/if_{addr,link}.h should be processed with unifdef.
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> Applied, thanks Adrian.
>
> I believe at least the 2.6.19 -stable branch will need
> this too, right? Please submit to -stable as needed,
> and feel free to add my sign-off:
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
All my patch does is to remove "#ifndef __KERNEL__"'s around userspace
#define's from the userspace headers, so it's purely cosmetical.
Except when userspace wrongly defines __KERNEL__, no
header-y<->unifdef-y should ever have any non-cosmetical effect.
That said, we really want what I called "cosmetical" - not having
"#if{,n}def __KERNEL__" in any userspace headers - it's simply that this
is not a serious bug.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2007-01-24 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 19:13 [2.6 patch] process include/linux/if_{addr,link}.h with unifdef Adrian Bunk
2007-01-24 6:05 ` David Miller
2007-01-24 10:20 ` Adrian Bunk [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=20070124102044.GG17836@stusta.de \
--to=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).