From: "S. Gilles" <sgilles@math.umd.edu>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com
Subject: Re: [BUG] brcmfmac: BRCM4354 cannot connect since commit 270a6c1f65
Date: Tue, 11 Jul 2017 10:56:17 -0400 [thread overview]
Message-ID: <20170711145617.puao7oybvpv3it72@number18.npnth.net> (raw)
In-Reply-To: <d5775426-f1bd-c2ce-89a8-e11472815787@broadcom.com>
On 2017-07-11T14:35:07+0200, Arend van Spriel wrote:
> [...]
>
> Looking at the diff of the bad commit, I came up with the patch below.
> Can you try it and let me know the result?
That seems to fix everything for me, thanks for the quick patch!
Thanks,
S. Gilles
prev parent reply other threads:[~2017-07-11 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 12:21 [BUG] brcmfmac: BRCM4354 cannot connect since commit 270a6c1f65 S. Gilles
2017-07-11 12:35 ` Arend van Spriel
2017-07-11 14:56 ` S. Gilles [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=20170711145617.puao7oybvpv3it72@number18.npnth.net \
--to=sgilles@math.umd.edu \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.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).