From: Ben Hutchings <ben@decadent.org.uk>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: stable@vger.kernel.org, Touko Korpela <touko.korpela@iki.fi>,
Arend van Spriel <arend@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: [PATCH 3.2.y, 3.3.y] brcm80211: smac: fix endless retry of A-MPDU transmissions
Date: Thu, 17 May 2012 01:05:47 +0100 [thread overview]
Message-ID: <1337213147.4107.59.camel@deadeye> (raw)
In-Reply-To: <20120516222824.GA11009@burratino>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
On Wed, 2012-05-16 at 17:28 -0500, Jonathan Nieder wrote:
> From: Arend van Spriel <arend@broadcom.com>
> Date: Thu, 9 Feb 2012 21:08:58 +0100
>
> commit 5e379203c7788b7af01150bfadbc74d2797a2ef4 upstream.
[...]
Added to the queue for 3.2.y.
Ben.
--
Ben Hutchings
Every program is either trivial or else contains at least one bug
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-17 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 17:38 [PATCH for 3.3 0/2] brcm80211: fix endless A-MPDU retries Arend van Spriel
2012-02-23 17:38 ` [PATCH 1/2] brcm80211: smac: fix endless retry of A-MPDU transmissions Arend van Spriel
2012-05-16 22:28 ` [PATCH 3.2.y, 3.3.y] " Jonathan Nieder
2012-05-17 0:05 ` Ben Hutchings [this message]
2012-05-18 19:58 ` Greg KH
2012-05-18 20:51 ` Jonathan Nieder
2012-05-19 8:49 ` Arend van Spriel
2012-05-19 16:53 ` Jonathan Nieder
2012-02-23 17:38 ` [PATCH 2/2] brcm80211: smac: only print block-ack timeout message at trace level Arend van Spriel
2012-11-24 23:14 ` [3.2.y] " Jonathan Nieder
2012-12-02 3:35 ` Ben Hutchings
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=1337213147.4107.59.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=arend@broadcom.com \
--cc=jrnieder@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.com \
--cc=stable@vger.kernel.org \
--cc=touko.korpela@iki.fi \
/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).