From: Joe Perches <joe@perches.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: remove spurious __KERNEL__ ifdef
Date: Thu, 30 Sep 2010 12:36:57 -0700 [thread overview]
Message-ID: <1285875417.9599.40.camel@Joe-Laptop> (raw)
In-Reply-To: <1285874485.5137.16.camel@jlt3.sipsolutions.net>
On Thu, 2010-09-30 at 21:21 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> The net/cfg80211.h header file isn't exported to
> userspace, so there's no need for any kind of
> __KERNEL__ protection in it. If it was exported,
> everything else in it would need protection as
> well, not just the logging stuff ...
>
> Cc:Joe Perches <joe@perches.com>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> Might be something that slipped in elsewhere too?
I thought John was going to remove that guard.
http://lkml.org/lkml/2010/7/27/294
I believe John removed the other one.
next prev parent reply other threads:[~2010-09-30 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 19:21 [PATCH] cfg80211: remove spurious __KERNEL__ ifdef Johannes Berg
2010-09-30 19:36 ` Joe Perches [this message]
2010-10-04 18:33 ` John W. Linville
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=1285875417.9599.40.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).