From: "Arend van Spriel" <arend@broadcom.com>
To: "Jonathan Nieder" <jrnieder@gmail.com>
Cc: Camaleón <noelamac@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"sgruszka@redhat.com" <sgruszka@redhat.com>,
"Seth Forshee" <seth.forshee@canonical.com>
Subject: Re: brcmsmac still woes, possible regression?
Date: Wed, 9 May 2012 12:32:20 +0200 [thread overview]
Message-ID: <4FAA47B4.5090002@broadcom.com> (raw)
In-Reply-To: <20120509102926.GD3499@burratino>
On 05/09/2012 12:29 PM, Jonathan Nieder wrote:
>
> Thanks for explaining. That makes sense.
>
> Is the short term fix badc4f07622f ("brcm80211: smac: resume transmit
> fifo upon receiving frames", 2012-04-11)?
>
> Thanks,
> Jonathan
>
Yep. I remember because the SHA1 start with 'bad', which felt like a
certain kind of omen to me ;-)
Gr. AvS
next prev parent reply other threads:[~2012-05-09 10:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 8:55 brcmsmac still woes, possible regression? Camaleón
2012-03-24 9:27 ` Arend van Spriel
2012-03-24 10:04 ` Camaleón
2012-03-24 11:21 ` Camaleón
2012-03-26 9:23 ` Arend van Spriel
2012-03-26 9:43 ` Camaleón
2012-03-26 10:10 ` Arend van Spriel
2012-03-26 21:28 ` Camaleón
2012-03-27 8:47 ` Arend van Spriel
2012-03-28 11:19 ` Arend van Spriel
2012-03-28 11:26 ` Camaleón
2012-03-28 12:23 ` Arend van Spriel
2012-03-28 21:59 ` Camaleón
2012-03-29 11:56 ` Arend van Spriel
2012-03-29 13:38 ` Camaleón
2012-04-02 13:29 ` Camaleón
2012-04-02 21:50 ` Jonathan Nieder
2012-04-03 6:25 ` Camaleón
2012-04-03 15:30 ` Arend van Spriel
2012-05-09 9:41 ` Jonathan Nieder
2012-05-09 10:23 ` Arend van Spriel
2012-05-09 10:29 ` Jonathan Nieder
2012-05-09 10:32 ` Arend van Spriel [this message]
2012-05-09 17:41 ` Seth Forshee
2012-05-09 18:01 ` Arend van Spriel
2012-05-09 18:10 ` Johannes Berg
2012-05-10 16:35 ` Seth Forshee
2012-05-11 9:32 ` Johannes Berg
2012-05-11 17:31 ` Seth Forshee
2012-05-16 20:15 ` Seth Forshee
2012-05-29 7:16 ` Johannes Berg
2012-03-26 14:32 ` Seth Forshee
2012-03-26 16:54 ` Arend van Spriel
2012-03-26 17:13 ` Seth Forshee
2012-03-26 17:15 ` 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=4FAA47B4.5090002@broadcom.com \
--to=arend@broadcom.com \
--cc=jrnieder@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=noelamac@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.