From: "Arend van Spriel" <arend@broadcom.com>
To: "Jonathan Nieder" <jrnieder@gmail.com>
Cc: "Stanislaw Gruszka" <sgruszka@redhat.com>,
linux-wireless@vger.kernel.org, Camaleón <noelamac@gmail.com>,
"Seth Forshee" <seth.forshee@canonical.com>,
"Roland Vossen" <rvossen@broadcom.com>
Subject: Re: [3.2.y] Re: Brcmsmac driver woes, possible regression?
Date: Wed, 20 Jun 2012 14:13:14 +0200 [thread overview]
Message-ID: <4FE1BE5A.2060808@broadcom.com> (raw)
In-Reply-To: <20120620100218.GA4579@burratino>
On 06/20/2012 12:02 PM, Jonathan Nieder wrote:
> Arend van Spriel wrote:
>> On 06/19/2012 09:28 PM, Jonathan Nieder wrote:
>
>>> I had been hoping that was mostly orthogonal until Camaleón mentioned
>>> that 3.2.2 doesn't seem to trigger the random reconnects.
>>
>> I missed this piece of info. So the following statements are true?
>>
>> 1. v3.2.2 and earlier did not show the issue.
>> 2. v3.2.9 until 3.2.17 have random reconnects.
>> 3. v3.2.18 does not have random reconnects (or less).
>
> (1) and (2) are true. I don't think (3) is.
>
I have my doubts on (3) as well, but I think the likelihood of the
random reconnects has reduced by earlier mentioned patches. I will work
with Camaleón and/or Touko Korpela investigating this (and keep you posted).
Gr. AvS
next prev parent reply other threads:[~2012-06-20 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKprTDFHmBuOorCo4evrYrNEi2-gJov0mQXQpEjoRJicfhWg=A@mail.gmail.com>
[not found] ` <20120530172713.GH3908@burratino>
[not found] ` <CAKprTDGtvUFSBb_XK01bi6bJa3dynu73Lq-jTs=E78E3QwSqpA@mail.gmail.com>
[not found] ` <20120601174237.GA31781@burratino>
[not found] ` <CAKprTDHepfbCKquvnG8CQ2=-tSNbgOSkT6R0GQmEx9UyuiZyMQ@mail.gmail.com>
[not found] ` <CAKprTDHQT8Oodh_YD5CWffSGJXAg-HgFMjR0STVgEZRxH4FaSQ@mail.gmail.com>
[not found] ` <20120604084200.GA30645@tiikeri.vuoristo.local>
[not found] ` <20120604173121.GA9238@stt008.linux.site>
[not found] ` <20120605050620.GC3118@burratino>
[not found] ` <CAKprTDHGqDpdZY4ErZmPEc7Ur81GeQoH8tiAL5hrfhAE0RtbvQ@mail.gmail.com>
2012-06-11 3:15 ` [3.2.y] Re: Brcmsmac driver woes, possible regression? Jonathan Nieder
2012-06-19 18:15 ` Jonathan Nieder
2012-06-19 19:15 ` Arend van Spriel
2012-06-19 19:28 ` Jonathan Nieder
2012-06-20 7:11 ` Arend van Spriel
2012-06-20 10:02 ` Jonathan Nieder
2012-06-20 12:13 ` Arend van Spriel [this message]
2012-06-19 18:51 ` Arend van Spriel
2012-07-07 4:56 ` Jonathan Nieder
2012-07-16 21:31 ` Jonathan Nieder
2012-07-17 7:54 ` Arend van Spriel
2012-07-23 0:28 ` Jonathan Nieder
2012-07-29 22:48 ` Jonathan Nieder
[not found] ` <20120610224902.GB3419@burratino>
[not found] ` <20120611063014.GA4579@stt008.linux.site>
[not found] ` <CAKprTDHYMyDwvxA52Z9zxP75ZUY5=FfCGPTZZg9ZxTxReFj7pQ@mail.gmail.com>
[not found] ` <20120619180335.GA19354@burratino>
[not found] ` <CAKprTDGM8TJC51Bqideeg447+qR5YnfihgORUFdJL_hW9YHiTw@mail.gmail.com>
2012-06-23 17:50 ` [3.2.y] " Jonathan Nieder
2012-06-24 9:41 ` Arend van Spriel
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=4FE1BE5A.2060808@broadcom.com \
--to=arend@broadcom.com \
--cc=jrnieder@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=noelamac@gmail.com \
--cc=rvossen@broadcom.com \
--cc=seth.forshee@canonical.com \
--cc=sgruszka@redhat.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).