Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Standardisation - adding 2 bit STBC and Ness to MCS
Date: Thu, 02 May 2013 22:44:39 +0200	[thread overview]
Message-ID: <1367527479.11375.19.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <518127ED.9060900@rempel-privat.de> (sfid-20130501_163425_421280_1DE3F635)

On Wed, 2013-05-01 at 16:34 +0200, Oleksij Rempel wrote:

> > With this I believe we have everything needed to start the 3 week
> > comment period.

Yeah, I guess there was plenty of time. I would have preferred a
separate thread, but I guess there's little enough traffic on this list
so it doesn't really matter.

> There is a bit more then 3 week now. I would like to have this approved :)
> Are there any thing needed to finish this?

http://www.radiotap.org/Standardisation

johannes

  reply	other threads:[~2013-05-02 20:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 14:34 [ath9k-devel] Standardisation - adding 2 bit STBC and Ness to MCS Oleksij Rempel
2013-05-02 20:44 ` Johannes Berg [this message]
2013-05-03 19:53   ` [ath9k-devel] Patches for STBC Standartisation Oleksij Rempel
2013-05-03 19:53     ` [ath9k-devel] [PATCH 1/3] mac80211: add STBC flag for radiotap Oleksij Rempel
2013-05-03 19:53     ` [ath9k-devel] [PATCH 2/3] ath9k: remove useless flag conversation Oleksij Rempel
2013-05-03 19:53     ` [ath9k-devel] [PATCH 3/3] ath9k: check for Rx-STBC flag and pass it to ieee80211 Oleksij Rempel
2013-05-03 19:53     ` [ath9k-devel] [PATCH] tcpdump: add STBC Rx support Oleksij Rempel
2013-05-03 19:58       ` Guy Harris
2013-05-03 20:04         ` Oleksij Rempel
2013-05-04  6:22     ` [ath9k-devel] Patch for radiotap library Oleksij Rempel
2013-05-07  7:40   ` [ath9k-devel] Standardisation - adding 2 bit STBC and Ness to MCS Oleksij Rempel
2013-05-07 13:54     ` Johannes Berg
2013-05-07 13:55       ` Johannes Berg
2013-05-07 14:25         ` Oleksij Rempel
2013-05-03 21:12 ` Simon Barber

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=1367527479.11375.19.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