[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F990BE8.60805@broadcom.com>
Date: Thu, 26 Apr 2012 10:48:40 +0200
From: "Arend van Spriel" <arend@...adcom.com>
To: "Jonathan Nieder" <jrnieder@...il.com>
cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
"Greg KH" <gregkh@...uxfoundation.org>, alan@...rguk.ukuu.org.uk,
"Francesco Saverio Schiavarelli" <fschiava@...ero.it>,
"Pieter-Paul Giesberts" <pieterpg@...adcom.com>,
"Brett Rudley" <brudley@...adcom.com>,
"John W. Linville" <linville@...driver.com>
Subject: Re: [ 23/62] brcm80211: smac: resume transmit fifo upon
receiving frames
On 04/26/2012 12:39 AM, Jonathan Nieder wrote:
> Greg KH wrote:
>
>> 3.3-stable review patch.
> [...]
>> commit badc4f07622f0f7093a201638f45e85765f1b5e4 upstream.
>>
>> There have been reports about not being able to use access-points
>> on channel 12 and 13 or having connectivity issues when these channels
>> were part of the selected regulatory domain. Upon switching to these
>> channels the brcmsmac driver suspends the transmit dma fifos. This
>> patch resumes them upon handing over the first received beacon to
>> mac80211.
>>
>> This patch is to be applied to the stable tree for kernel versions
>> 3.2 and 3.3.
>
> Here's a blind backport to 3.0.y for the next cycle. Nothing scary
> involved, though of course it's completely untested. Sensible?
>
> Thanks,
> Jonathan
We decided to only submit the patch for the mainline version of the
driver, but your changes on the staging driver look fine. So if this
patch is accepted in stable it is
Acked-by: Arend van Spriel <arend@...adcom.com>
Gr. AvS
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists