From: Karl Beldan <karl.beldan@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Karl Beldan <karl.beldan@rivierawaves.com>,
Helmut Schaa <helmut.schaa@googlemail.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: [PATCH v2] mac80211: send {ADD,DEL}BA on AC_VO like other mgmt frames, as per spec
Date: Thu, 23 Jan 2014 20:38:10 +0100 [thread overview]
Message-ID: <20140123193809.GA22546@gobelin> (raw)
In-Reply-To: <1390504524.4142.39.camel@jlt4.sipsolutions.net>
On Thu, Jan 23, 2014 at 08:15:24PM +0100, Johannes Berg wrote:
> On Thu, 2014-01-23 at 20:06 +0100, Karl Beldan wrote:
> > From: Karl Beldan <karl.beldan@rivierawaves.com>
> >
> > ATM, {ADD,DEL}BA and BAR frames are sent on the AC matching the TID of
> > the BA parameters. Johannes recalled [1] that it fixed some races with
> > the DELBA and indeed this behavior was introduced in [2].
>
> Applied. I made some minor edits to the commit log, notably to fix that
> you had too many [2] (I guess originally you wanted to link to all the
> different emails?)
>
Yes, only the 2 first [2]s were intended [2]s .. in the very end of the
day I had to struggle to write this, I guess it shows.
Karl
prev parent reply other threads:[~2014-01-23 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 11:52 [PATCH] mac80211: send {add,del}ba on AC_VO like other mgmt frames, as per spec Karl Beldan
2014-01-22 12:34 ` Johannes Berg
2014-01-22 13:09 ` Karl Beldan
2014-01-22 13:33 ` Helmut Schaa
2014-01-22 15:28 ` Karl Beldan
2014-01-22 15:36 ` Helmut Schaa
2014-01-22 16:41 ` Karl Beldan
2014-01-22 18:51 ` Johannes Berg
2014-01-22 19:16 ` Karl Beldan
2014-01-22 19:21 ` Johannes Berg
2014-01-22 20:47 ` Helmut Schaa
2014-01-23 6:08 ` Grumbach, Emmanuel
2014-01-23 13:42 ` Helmut Schaa
2014-01-23 14:08 ` Johannes Berg
2014-01-23 19:06 ` [PATCH v2] mac80211: send {ADD,DEL}BA " Karl Beldan
2014-01-23 19:15 ` Johannes Berg
2014-01-23 19:38 ` Karl Beldan [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=20140123193809.GA22546@gobelin \
--to=karl.beldan@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=helmut.schaa@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=karl.beldan@rivierawaves.com \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.