From: Mehmet Fide <mehmet.fide@gmail.com>
To: Michail Andreas Michalopoulos <mike.michalo@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
"Pengpeng Hou" <pengpeng@iscas.ac.cn>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
mehmet.fide@screeningeagle.com
Subject: Re: [PATCH 0/2] wifi: ath9k: fix WMI command response handling
Date: Wed, 21 Oct 2026 00:46:44 +0200 [thread overview]
Message-ID: <20261020224644.3858280-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <20261020152412.95560-1-mike.michalo@gmail.com>
Hi Michail,
On 2026-10-20, Michail Andreas Michalopoulos wrote:
> I don't have access to an ath9k_htc device, so this was not tested on
> hardware. Mehmet, if you could give it a try on your AR9271 that would
> be much appreciated.
Tested on an AR9271 with firmware 1.4 as an AP, on 6.12.113 with the
revert of 93ce8ea70451.
The AP comes up and works; the empty responses the firmware sends for
most commands complete as before. A test build that delivered responses
twice had every duplicate dropped, and with tx_seq_id started just below
the wrap, 0 was never sent. hostapd restarts, module reloads, USB
unbind/bind and a 30 minute soak with traffic ran without a WMI timeout
or a kernel warning.
Tested-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
Thanks,
Mehmet
next prev parent reply other threads:[~2026-10-20 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:24 Michail Andreas Michalopoulos
2026-10-20 15:24 ` [PATCH 1/2] wifi: ath9k: don't read past short WMI command responses Michail Andreas Michalopoulos
2026-10-20 15:24 ` [PATCH 2/2] wifi: ath9k: drop WMI command responses when no command is pending Michail Andreas Michalopoulos
2026-10-20 22:46 ` Mehmet Fide [this message]
2026-10-20 23:19 ` [PATCH 0/2] wifi: ath9k: fix WMI command response handling mixalhs
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=20261020224644.3858280-1-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mehmet.fide@screeningeagle.com \
--cc=mike.michalo@gmail.com \
--cc=pengpeng@iscas.ac.cn \
--cc=toke@toke.dk \
/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
all inboxes | Powered by JetHome®