From: Jonathan Nieder <jrnieder@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Greg KH <greg@kroah.com>,
stable@vger.kernel.org, Touko Korpela <touko.korpela@iki.fi>,
"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: Sat, 19 May 2012 11:53:16 -0500 [thread overview]
Message-ID: <20120519165316.GC26095@burratino> (raw)
In-Reply-To: <4FB75E88.3010908@broadcom.com>
Arend van Spriel wrote:
> On 05/18/2012 10:51 PM, Jonathan Nieder wrote:
>> My bad --- looks like it was already applied during the 3.3 cycle as
>> v3.3~19^2^2~7 (commit 85091fc0a756). Sorry I missed that before.
[...]
> Yes. The patch was posted upstream with Cc to stable. As it did not
> apply to earlier kernels it was marked for 3.3 stable only.
Technically it wasn't cc-ed to stable; it went to wireless-next
for 3.4 and then was fast-tracked through the plain wireless tree
for 3.3[1]. But the effect is basically the same.
Thanks for writing it.
Jonathan
[1] http://thread.gmane.org/gmane.linux.kernel.wireless.general/85902
http://thread.gmane.org/gmane.linux.kernel.wireless.general/85249
next prev parent reply other threads:[~2012-05-19 16:53 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
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 [this message]
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=20120519165316.GC26095@burratino \
--to=jrnieder@gmail.com \
--cc=arend@broadcom.com \
--cc=greg@kroah.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