radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: Re: [RFA] MCS extension
Date: Thu, 27 Jan 2011 14:09:45 +0100	[thread overview]
Message-ID: <1296133785.3622.34.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20110121164137.GD24244-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>

On Fri, 2011-01-21 at 10:41 -0600, David Young wrote:
> On Fri, Jan 21, 2011 at 11:08:01AM +0100, Johannes Berg wrote:
> > On Sat, 2010-12-18 at 18:56 +0100, Johannes Berg wrote:
> > > This is a request for adoption of a new version of the MCS extension.
> > > I've split out the aMPDU extension since that seems more natural.
> > > 
> > > The MCS extension allows giving MCS information about a frame.
> > 
> > Any notes on this? Nobody objecting to the split between MCS and a-MPDU
> > that I now did? :-)
> 
> Thanks for the reminder.  Radiotap emails keep slipping over my email
> horizon. :-/
> 
> Looks good to me.  Thanks for doing this.

Thanks for looking, I got behind too. I've made the corresponding wiki
change now, and will go ahead and submit the patches I'd done.

Thanks! A-MPDU is next, and maybe those TX flags and retry things.

johannes

      parent reply	other threads:[~2011-01-27 13:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-18 17:56 [RFA] MCS extension Johannes Berg
     [not found] ` <1292694998.3653.33.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2011-01-21 10:08   ` Johannes Berg
     [not found]     ` <1295604481.3831.1.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2011-01-21 16:41       ` David Young
     [not found]         ` <20110121164137.GD24244-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2011-01-27 13:09           ` 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=1296133785.3622.34.camel@jlt3.sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@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).