linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Karthikeyan Kathirvel <kathirve@codeaurora.org>,
	Sven Eckelmann <sven@narfation.org>
Subject: Re: [PATCH v2 1/2] ath11k: clear the keys properly via DISABLE_KEY
Date: Wed, 17 Nov 2021 07:32:57 +0000 (UTC)	[thread overview]
Message-ID: <163713437291.31320.11796327341306662079.kvalo@codeaurora.org> (raw)
In-Reply-To: <20211115100441.33771-1-sven@narfation.org>

Sven Eckelmann <sven@narfation.org> wrote:

> DISABLE_KEY sets the key_len to 0, firmware will not delete the keys if
> key_len is 0. Changing from security mode to open mode will cause mcast
> to be still encrypted without vdev restart.
> 
> Set the proper key_len for DISABLE_KEY cmd to clear the keys in
> firmware.
> 
> Tested-on: IPQ6018 hw1.0 AHB WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1
> 
> Fixes: d5c65159f289 ("ath11k: driver for Qualcomm IEEE 802.11ax devices")
> Reported-by: Sven Eckelmann <sven@narfation.org>
> Signed-off-by: Karthikeyan Kathirvel <kathirve@codeaurora.org>
> [sven@narfation.org: split into separate patches, clean up commit message]
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

2 patches applied to ath-next branch of ath.git, thanks.

436a4e886598 ath11k: clear the keys properly via DISABLE_KEY
64bc3aa02ae7 ath11k: reset RSN/WPA present state for open BSS

-- 
https://patchwork.kernel.org/project/linux-wireless/patch/20211115100441.33771-1-sven@narfation.org/

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


      parent reply	other threads:[~2021-11-17  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 10:04 [PATCH v2 1/2] ath11k: clear the keys properly via DISABLE_KEY Sven Eckelmann
2021-11-15 10:04 ` [PATCH v2 2/2] ath11k: reset RSN/WPA present state for open BSS Sven Eckelmann
2021-11-17  7:32 ` 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=163713437291.31320.11796327341306662079.kvalo@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=kathirve@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sven@narfation.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).