From: Greg KH <gregkh@linuxfoundation.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: stable@vger.kernel.org,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@nbd.name>, Sid Hayn <sidhayn@gmail.com>
Subject: Re: [PATCH 4.19] mt76x0: mark 802.11w as supported
Date: Thu, 20 Dec 2018 13:30:55 +0100 [thread overview]
Message-ID: <20181220123055.GC17138@kroah.com> (raw)
In-Reply-To: <20181220114701.GA8660@redhat.com>
On Thu, Dec 20, 2018 at 12:47:07PM +0100, Stanislaw Gruszka wrote:
> commit 0ae976a11b4fb5704b597e103b5189237641c1a1 upstream.
>
> This is one line hw feature backport from 0ae976a11b4f ("mt76x0: init
> hw capabilities"), which add also other different features, however
> those are not supported in 4.19.
>
> 802.11w is supported by mac80211 and mt76x0u driver in 4.19 correctly
> fall-back to software encryption when 802.11w ciphers are used.
>
> Without the patch we fail to associate with WPA3 APs, so this is
> considered as fix.
>
> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
> Signed-off-by: Felix Fietkau <nbd@nbd.name>
> [remove marking non-working features on 4.19, make topic correspond the change]
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
> drivers/net/wireless/mediatek/mt76/mt76x0/init.c | 1 +
> 1 file changed, 1 insertion(+)
What bug is this fixing? This never worked before, so this feels like
it is adding a new feature.
thanks,
greg k-h
next prev parent reply other threads:[~2018-12-20 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 11:47 [PATCH 4.19] mt76x0: mark 802.11w as supported Stanislaw Gruszka
2018-12-20 12:30 ` Greg KH [this message]
2018-12-20 13:17 ` Stanislaw Gruszka
2018-12-20 14:30 ` Sid Hayn
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=20181220123055.GC17138@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=sgruszka@redhat.com \
--cc=sidhayn@gmail.com \
--cc=stable@vger.kernel.org \
/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).