From: Kalle Valo <kvalo@codeaurora.org>
To: Rakesh Pillai <pillair@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Re: [PATCH v2 0/2] ath10k: Fixes during subsystem recovery
Date: Mon, 21 Dec 2020 20:37:01 +0200 [thread overview]
Message-ID: <87k0tbngz6.fsf@codeaurora.org> (raw)
In-Reply-To: <1593197633-9014-1-git-send-email-pillair@codeaurora.org> (Rakesh Pillai's message of "Sat, 27 Jun 2020 00:23:51 +0530")
Rakesh Pillai <pillair@codeaurora.org> writes:
> This patch series includes some fixes when the device
> is in recovery mode, i.e. when the firmware goes down.
>
> - Pausing TX queues when FW goes down
> - Removed unwanted/extra error logging in pkt TX path
> - Skipping wait for FW response for delete cmds
> - Handling the -ESHUTDOWN error code in case of SSR.
>
> Rakesh Pillai (2):
> ath10k: Pause the tx queues when firmware is down
> ath10k: Skip wait for delete response if firmware is down
This has been tested only on WCN3990. How do I know that this doesn't
break other hardware families?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-12-21 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 18:53 [PATCH v2 0/2] ath10k: Fixes during subsystem recovery Rakesh Pillai
2020-06-26 18:53 ` [PATCH v2 1/2] ath10k: Pause the tx queues when firmware is down Rakesh Pillai
2020-06-26 18:53 ` [PATCH v2 2/2] ath10k: Skip wait for delete response if " Rakesh Pillai
2020-09-15 7:47 ` [PATCH v2 0/2] ath10k: Fixes during subsystem recovery Rakesh Pillai
2020-09-15 14:28 ` Kalle Valo
2020-12-21 18:37 ` Kalle Valo [this message]
2021-01-15 13:25 ` Rakesh Pillai
2021-02-26 14:40 ` Rakesh Pillai
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=87k0tbngz6.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pillair@codeaurora.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).