From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
Cc: radiotap-qavaossjCcEdnm+yROfE0A@public.gmane.org,
simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org,
"ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org"
<ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Standardisation - adding 2 bit STBC and Ness to MCS (repost 3)
Date: Thu, 16 May 2013 15:22:03 +0200 [thread overview]
Message-ID: <1368710523.8387.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5194A06A.3000103-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org> (sfid-20130516_110137_244706_0B9B5695)
On Thu, 2013-05-16 at 11:01 +0200, Oleksij Rempel wrote:
> Hallo all,
>
> so, there is no updates or critic on this topic. That mean, every thing
> is OK.
I tend to agree.
> I assume "suggested-fields/MCS extension for STBC and Ness"
> http://www.radiotap.org/suggested-fields/MCS%20extension%20for%20STBC%20and%20Ness
>
> can be moved to "defined-fields/MCS"
> http://www.radiotap.org/defined-fields/MCS
>
> Johannes, your word ;)
I don't really have any say, but go for it, for all I care :)
johannes
next prev parent reply other threads:[~2013-05-16 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <518B72AE.4010402@rempel-privat.de>
[not found] ` <518B72AE.4010402-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-16 9:01 ` Standardisation - adding 2 bit STBC and Ness to MCS (repost 3) Oleksij Rempel
[not found] ` <5194A06A.3000103-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-16 13:22 ` Johannes Berg [this message]
2013-05-09 9:55 Oleksij Rempel
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=1368710523.8387.5.camel@jlt4.sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org \
--cc=linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=radiotap-qavaossjCcEdnm+yROfE0A@public.gmane.org \
--cc=simon-vp0mx6+5gkqFX2APIN6yfw@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).