From: "Jouni Malinen" <jkm@devicescape.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: jketreno <jketreno@linux.intel.com>,
yi.zhu@intel.com, linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Michael Wu <flamingice@sourmilk.net>
Subject: Re: [PATCH 1/3] mac80211: add IEEE802.11e/WMM structures
Date: Thu, 7 Jun 2007 15:59:49 -0700 [thread overview]
Message-ID: <20070607225949.GL26739@devicescape.com> (raw)
In-Reply-To: <20070608004909.7322f394@logostar.upir.cz>
On Fri, Jun 08, 2007 at 12:49:09AM +0200, Jiri Benc wrote:
> On Thu, 07 Jun 2007 21:32:33 -0700, jketreno wrote:
> > It doesn't really look like he invented a 'new useless' prefix. It looks
> > to me like he picked a prefix that correlates attribution of the data
> > declaration to the entity that created it. You may not like that he
> > provided attribution, but that doesn't mean its useless.
>
> By "useless", I meant "if you use a WLAN_ prefix like in all other #defines
> in that file, it will do the same job". Ok, I understand the argument about
> attribution, but it shouldn't be in exchange of consistency and clarity.
WLAN_ prefix is currently mostly (only?) used for values defined in
IEEE 802.11 while the WMM parameters are defined in WFA specification,
not IEEE 802.11.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-06-07 22:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 8:22 [PATCH 1/3] mac80211: add IEEE802.11e/WMM structures Zhu Yi
2007-06-07 20:30 ` Jiri Benc
2007-06-08 1:34 ` Zhu Yi
2007-06-08 7:23 ` Johannes Berg
2007-06-08 10:07 ` Jiri Benc
2007-06-08 4:32 ` jketreno
2007-06-07 22:49 ` Jiri Benc
2007-06-07 22:59 ` Jouni Malinen [this message]
2007-06-08 2:14 ` Michael Wu
2007-06-08 3:40 ` Zhu Yi
2007-06-08 10:16 ` Jiri Benc
2007-06-08 16:38 ` Zhu Yi
-- strict thread matches above, loose matches on Subject: below --
2007-05-25 11:52 Zhu Yi
2007-05-14 5:15 Zhu Yi
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=20070607225949.GL26739@devicescape.com \
--to=jkm@devicescape.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=jketreno@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@intel.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 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.