From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Vladimir Zapolskiy" <vz@mleia.com>,
linux-wireless@vger.kernel.org, brcm80211-dev-list@broadcom.com
Subject: Re: [PATCH] brcm80211: smac: set interface down on reset
Date: Mon, 13 Aug 2012 22:05:54 +0200 [thread overview]
Message-ID: <50295E22.2010705@broadcom.com> (raw)
In-Reply-To: <20120813185042.GD10529@tuxdriver.com>
On 08/13/2012 08:50 PM, John W. Linville wrote:
> On Mon, Aug 06, 2012 at 09:45:33PM +0200, Arend van Spriel wrote:
>> On 08/06/2012 09:39 PM, Vladimir Zapolskiy wrote:
>>> Hi Arend,
>>>
>>> what do you think about the proposed change? For me the problem is
>>> quite severe, for the last several months I had to patch the kernel
>>> to have functional BCM43225 on my laptop, hopefully the fix should go to
>>> the
>>> stable branches as well.
>>>
>>
>> I have forwarded it to my colleagues. I may want to revise the fix a
>> little and have it applied to stable as well. I was not aware that this
>> scenario occurs frequently. Thanks for addressing your issue so
>> proactively ;-)
>
> Any word on the state of this fix?
>
> John
>
Hi John,
This change was briefly discussed internally. The patch will
reinitialize the entire driver and device. While this probably works it
may be overkill. OTOH it is better that than no solution. I suggest to
apply this and have us come up with a more definite fix later at which
we can move both patches to stable.
Gr. AvS
prev parent reply other threads:[~2012-08-13 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 21:29 [PATCH] brcm80211: smac: set interface down on reset Vladimir Zapolskiy
2012-08-06 19:39 ` Vladimir Zapolskiy
2012-08-06 19:45 ` Arend van Spriel
2012-08-06 20:06 ` Vladimir Zapolskiy
2012-08-13 18:50 ` John W. Linville
2012-08-13 20:05 ` Arend van Spriel [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=50295E22.2010705@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=vz@mleia.com \
/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).