From: Kalle Valo <kvalo@codeaurora.org>
To: ath11k@lists.infradead.org
Subject: Re: [PATCH 0/6] ath11k: QCA6390 stability fixes
Date: Thu, 10 Dec 2020 16:14:50 +0200 [thread overview]
Message-ID: <87r1nx4ujp.fsf@codeaurora.org> (raw)
In-Reply-To: <1607609124-17250-1-git-send-email-kvalo@codeaurora.org> (Kalle Valo's message of "Thu, 10 Dec 2020 16:05:18 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> Few fixes to improve statibility on QCA6390. Please review.
>
> Kalle
>
> Carl Huang (4):
> ath11k: put hw to DBS using WMI_PDEV_SET_HW_MODE_CMDID
> ath11k: pci: fix hot reset stability issues
> ath11k: pci: fix L1ss clock unstable problem
> ath11k: pci: disable VDD4BLOW
>
> Kalle Valo (1):
> ath11k: mhi: print a warning if firmware crashed
>
> Pradeep Kumar Chitrapu (1):
> ath11k: Fix incorrect tlvs in scan start command
Forgot to mention that these fixes are just cleaned up versions from
ath11k-qca6390-bringup branch prepared to go to v5.11, so nothing new
here for QCA6390 testing point of view.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2020-12-10 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 14:05 [PATCH 0/6] ath11k: QCA6390 stability fixes Kalle Valo
2020-12-10 14:05 ` [PATCH 1/6] ath11k: mhi: print a warning if firmware crashed Kalle Valo
2020-12-12 4:40 ` Kalle Valo
2020-12-10 14:05 ` [PATCH 2/6] ath11k: put hw to DBS using WMI_PDEV_SET_HW_MODE_CMDID Kalle Valo
2020-12-10 14:05 ` [PATCH 3/6] ath11k: pci: fix hot reset stability issues Kalle Valo
2020-12-10 14:05 ` [PATCH 4/6] ath11k: pci: fix L1ss clock unstable problem Kalle Valo
2020-12-10 14:05 ` [PATCH 5/6] ath11k: pci: disable VDD4BLOW Kalle Valo
2020-12-10 22:04 ` Peter Oh
2020-12-11 6:31 ` Kalle Valo
2020-12-10 14:05 ` [PATCH 6/6] ath11k: Fix incorrect tlvs in scan start command Kalle Valo
2020-12-10 14:14 ` Kalle Valo [this message]
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=87r1nx4ujp.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.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