From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] 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@rempel-privat.de> (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
prev parent reply other threads:[~2013-05-16 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 9:55 [ath9k-devel] Standardisation - adding 2 bit STBC and Ness to MCS (repost 3) Oleksij Rempel
2013-05-16 9:01 ` Oleksij Rempel
2013-05-16 13:22 ` 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=1368710523.8387.5.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.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