From: Kalle Valo <kvalo@codeaurora.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
"open list\:TI WILINK WIRELES..."
<linux-wireless@vger.kernel.org>,
"open list\:BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER"
<brcm80211-dev-list.pdl@broadcom.com>,
brcm80211-dev-list@cypress.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
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>
Subject: Re: [PATCH] brcmfmac: fix wrong location to get firmware feature
Date: Mon, 30 Mar 2020 13:16:12 +0300 [thread overview]
Message-ID: <87r1xaf8r7.fsf@codeaurora.org> (raw)
In-Reply-To: <CAHp75Vey9VUSAT6j6NTSXqNUK1vwSqY=aSx3-WPoXgxCK33SDg@mail.gmail.com> (Andy Shevchenko's message of "Mon, 30 Mar 2020 12:08:27 +0300")
Andy Shevchenko <andy.shevchenko@gmail.com> writes:
> On Mon, Mar 30, 2020 at 8:26 AM Jaehoon Chung <jh80.chung@samsung.com> wrote:
>>
>> sup_wpa feature is getting after setting feature_disable flag.
>> If firmware is supported sup_wpa feature, it's always enabled
>> regardless of feature_disable flag.
>>
>
>> Fixes: b8a64f0e96c2 ("brcmfmac: support 4-way handshake offloading for WPA/WPA2-PSK")
>>
>> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
>
> No blank line in between. (Dunno if you need to resend, just wait what
> maintainer says)
I can fix that during commit, no need to resend because of this.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-03-30 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200330052521epcas1p1eedc926d4b11513f8502cf0c90ecf433@epcas1p1.samsung.com>
2020-03-30 5:25 ` [PATCH] brcmfmac: fix wrong location to get firmware feature Jaehoon Chung
2020-03-30 9:08 ` Andy Shevchenko
2020-03-30 10:16 ` Kalle Valo [this message]
2020-04-01 10:20 ` Jaehoon Chung
2020-04-14 15:03 ` Kalle Valo
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=87r1xaf8r7.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=andy.shevchenko@gmail.com \
--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=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.