From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Peter Seiderer <ps.report@gmx.net>, linux-wireless@vger.kernel.org
Cc: Kalle Valo <kvalo@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sujith Manoharan <c_manoha@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Gregg Wonderly <greggwonderly@seqtechllc.com>,
Simon Horman <simon.horman@corigine.com>,
Peter Seiderer <ps.report@gmx.net>
Subject: Re: [PATCH v2] wifi: ath9k: fix AR9003 mac hardware hang check register offset calculation
Date: Sun, 23 Apr 2023 13:30:25 +0200 [thread overview]
Message-ID: <87mt2yltta.fsf@toke.dk> (raw)
In-Reply-To: <20230422212423.26065-1-ps.report@gmx.net>
Peter Seiderer <ps.report@gmx.net> writes:
> Fix ath9k_hw_verify_hang()/ar9003_hw_detect_mac_hang() register offset
> calculation (do not overflow the shift for the second register/queues
> above five, use the register layout described in the comments above
> ath9k_hw_verify_hang() instead).
>
> Fixes: 222e04830ff0 ("ath9k: Fix MAC HW hang check for AR9003")
>
> Reported-by: Gregg Wonderly <greggwonderly@seqtechllc.com>
> Link: https://lore.kernel.org/linux-wireless/E3A9C354-0CB7-420C-ADEF-F0177FB722F4@seqtechllc.com/
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Alright, better, thanks! Let's try this again:
Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
next prev parent reply other threads:[~2023-04-23 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 21:24 [PATCH v2] wifi: ath9k: fix AR9003 mac hardware hang check register offset calculation Peter Seiderer
2023-04-23 11:30 ` Toke Høiland-Jørgensen [this message]
2023-04-23 17:50 ` Simon Horman
2023-04-28 16:51 ` 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=87mt2yltta.fsf@toke.dk \
--to=toke@toke.dk \
--cc=c_manoha@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=greggwonderly@seqtechllc.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ps.report@gmx.net \
--cc=simon.horman@corigine.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 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).