radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Simon Barber <simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
Cc: Wojciech Dubowik
	<wojciech.dubowik-ASv44eHyqLVBDgjK7y7TUQ@public.gmane.org>,
	radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Re: MCS field - STBC and Ness
Date: Mon, 05 Nov 2012 15:35:04 +0100	[thread overview]
Message-ID: <1352126104.9466.14.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <509312DB.7070100-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>

On Thu, 2012-11-01 at 17:24 -0700, Simon Barber wrote:
> OK - I have now posted 3 patches on the proposal page (see Attachments):
> 
> 1. A patch that applies to the Linux kernel v3.7-rc1 to collect the new 
> STBC and Ness parameters from a wireless driver, and add them into the 
> MCS radiotap field.
> 2. A patch to the Intel wireless driver in the kernel to collect STBC 
> and Ness information.
> 3. A patch to wireshark to display STBC and Ness information.

Nice!

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

Might be worthwhile to post a new thread so it gets everybody's
attention?

johannes

  parent reply	other threads:[~2012-11-05 14:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11  0:31 MCS field - STBC and Ness Simon Barber
     [not found] ` <4FAC5DE0.90708-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-05-11  7:04   ` Wojciech Dubowik
     [not found]     ` <4FACBA13.9040509-ASv44eHyqLVBDgjK7y7TUQ@public.gmane.org>
2012-05-11 16:44       ` Simon Barber
     [not found]         ` <4FAD41E4.3090803-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-05-11 16:53           ` Simon Barber
     [not found]             ` <4FAD43F0.20807-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-05-11 18:35               ` Johannes Berg
     [not found]                 ` <1336761346.8739.3.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-05-12  4:27                   ` Simon Barber
     [not found]                     ` <4FADE69F.9040100-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-07-05  9:12                       ` Johannes Berg
     [not found]                         ` <1341479550.4455.36.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-11-01  0:22                           ` Simon Barber
     [not found]                             ` <5091C0BC.4040305-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-11-02  0:24                               ` Simon Barber
     [not found]                                 ` <509312DB.7070100-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-11-05 14:35                                   ` Johannes Berg [this message]
2012-11-17  6:32                                   ` Standardisation - adding 2 bit STBC and Ness to MCS Simon Barber
2012-07-04 17:06   ` MCS field - STBC and Ness David Young

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=1352126104.9466.14.camel@jlt4.sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
    --cc=simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org \
    --cc=wojciech.dubowik-ASv44eHyqLVBDgjK7y7TUQ@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).