All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com,
	brcm80211-dev-list@cypress.com, linux-kernel@vger.kernel.org,
	arend.vanspriel@broadcom.com, franky.lin@broadcom.com,
	hante.meuleman@broadcom.com, chi-hsien.lin@cypress.com,
	wright.feng@cypress.com, Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: [PATCH] brcmfmac: fix wrong location to get firmware feature
Date: Tue, 14 Apr 2020 15:03:25 +0000 (UTC)	[thread overview]
Message-ID: <20200414150326.024A9C44798@smtp.codeaurora.org> (raw)
In-Reply-To: <20200330052528.10503-1-jh80.chung@samsung.com>

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>

Patch applied to wireless-drivers-next.git, thanks.

c57673852062 brcmfmac: fix wrong location to get firmware feature

-- 
https://patchwork.kernel.org/patch/11464609/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      parent reply	other threads:[~2020-04-14 15:03 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
2020-04-01 10:20       ` Jaehoon Chung
2020-04-14 15:03   ` Kalle Valo [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=20200414150326.024A9C44798@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --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.