From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Jiri Benc <jbenc@suse.cz>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: don't export linux/ieee80211.h
Date: Fri, 27 Apr 2007 22:17:40 +0200 [thread overview]
Message-ID: <1177705060.3565.55.camel@johannes.berg> (raw)
In-Reply-To: <200704271554.55770.flamingice@sourmilk.net>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
On Fri, 2007-04-27 at 15:54 -0400, Michael Wu wrote:
> The definitions in linux/ieee80211.h don't need to be exported.
Actually, cfg80211 depends on the cipher suite defines. These are of
course well-known constants and can be found in the specs, but I don't
see the point of not just exporting them.
Does anybody remember a reason why this should not be exported?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-04-27 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 19:54 [PATCH] mac80211: don't export linux/ieee80211.h Michael Wu
2007-04-27 20:17 ` Johannes Berg [this message]
2007-04-27 20:22 ` Michael Buesch
2007-04-27 20:30 ` Michael Wu
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=1177705060.3565.55.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=linux-wireless@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