From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Wojciech Dubowik
<Wojciech.Dubowik-ASv44eHyqLVBDgjK7y7TUQ@public.gmane.org>
Cc: radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Re: [RFC] MCS Field: STBC flag
Date: Wed, 02 Nov 2011 09:44:59 +0100 [thread overview]
Message-ID: <1320223499.3950.30.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <loom.20111101T094927-66-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
On Tue, 2011-11-01 at 09:34 +0000, Wojciech Dubowik wrote:
> Hello,
> I have been doing some testing with STBC and I have noticed that it's not
> available in radiotap fields.
> We could add new flag to MCS field to support it:
That seems useful.
I think even for new bits we should follow the regular process, see
http://radiotap.org/Standardisation (and examples on this list of
course)
johannes
prev parent reply other threads:[~2011-11-02 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 9:34 [RFC] MCS Field: STBC flag Wojciech Dubowik
[not found] ` <loom.20111101T094927-66-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-11-02 8:44 ` Johannes Berg [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=1320223499.3950.30.camel@jlt3.sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=Wojciech.Dubowik-ASv44eHyqLVBDgjK7y7TUQ@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.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).