From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
Karthikeyan Kathirvel <kathirve@codeaurora.org>
Subject: Re: [PATCH] ath11k: clear the keys properly when DISABLE_KEY
Date: Wed, 27 Oct 2021 08:12:35 +0200 [thread overview]
Message-ID: <26869605.A2Tbvc0WiF@ripper> (raw)
In-Reply-To: <20211026155446.457935-1-sven@narfation.org>
On Tuesday, 26 October 2021 17:54:46 CEST Sven Eckelmann wrote:
> Tested-on: IPQ6018 hw1.0 AHB WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1
I would like to retract this Tested-on. My test caused another problem which
resulted in a complete shutdown of the vdev. After fixing this problem, it
turned out that this change didn't fix anything (as far as I can see) on this
firmware version.
Kind regards,
Sven
next prev parent reply other threads:[~2021-10-27 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 15:54 [PATCH] ath11k: clear the keys properly when DISABLE_KEY Sven Eckelmann
2021-10-26 18:22 ` Sven Eckelmann
2021-10-27 6:12 ` Sven Eckelmann [this message]
2021-10-28 12:38 ` Kalle Valo
2021-10-28 12:43 ` Sven Eckelmann
2021-11-01 12:53 ` 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=26869605.A2Tbvc0WiF@ripper \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=kathirve@codeaurora.org \
--cc=linux-wireless@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).