From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Sven Eckelmann <se@simonwunderlich.de>,
ih@simonwunderlich.de, Issam Hamdi <ih@simonwunderlich.de>,
sw@simonwunderlich.de
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
mathias.kretschmer@fit.fraunhofer.de
Subject: Re: [PATCH v2 2/2] wifi: ath9k: Reset chip on potential deaf state
Date: Wed, 06 Nov 2024 13:41:27 +0100 [thread overview]
Message-ID: <87pln87cw8.fsf@toke.dk> (raw)
In-Reply-To: <865447434.0ifERbkFSE@ripper>
Sven Eckelmann <se@simonwunderlich.de> writes:
> Overall, the proposal from Toke seems to be a lot better integrated in the HW
> check style which was introduced by Felix in the beginning of 2017 [1].
>
> At the same time there was a proposal by Felix [2] - which diverged too much
> from our original patch (and as a result caused too many resets) [3]. I would
> therefore propose to check Toke's version and test handles the problem
> correctly.
Yes, agreed. I did actually write up a commit message for that, let me
send it as a proper patch...
-Toke
next prev parent reply other threads:[~2024-11-06 12:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 17:16 [PATCH 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang Issam Hamdi
2024-11-04 17:16 ` [PATCH 2/2] wifi: ath9k: Reset chip on potential deaf state Issam Hamdi
2024-11-05 10:53 ` Kalle Valo
2024-11-05 13:02 ` Toke Høiland-Jørgensen
2024-11-05 13:30 ` Simon Wunderlich
2024-11-05 15:10 ` Toke Høiland-Jørgensen
2024-11-06 10:05 ` Hamdi Issam
2024-11-05 13:34 ` Simon Wunderlich
2024-11-05 10:49 ` [PATCH 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang Kalle Valo
2024-11-05 12:31 ` Toke Høiland-Jørgensen
2024-11-06 9:04 ` [PATCH v2 " Issam Hamdi
2024-11-06 9:04 ` [PATCH v2 2/2] wifi: ath9k: Reset chip on potential deaf state Issam Hamdi
2024-11-06 10:05 ` Sven Eckelmann
2024-11-06 12:41 ` Toke Høiland-Jørgensen [this message]
2024-11-07 8:03 ` Kalle Valo
2024-11-06 10:06 ` [PATCH v2 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang Sven Eckelmann
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=87pln87cw8.fsf@toke.dk \
--to=toke@kernel.org \
--cc=ih@simonwunderlich.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fit.fraunhofer.de \
--cc=se@simonwunderlich.de \
--cc=sw@simonwunderlich.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.