From: Kalle Valo <kvalo@codeaurora.org>
To: Baochen Qiang <bqiang@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/7] ath11k: support one MSI vector
Date: Mon, 15 Nov 2021 12:30:10 +0200 [thread overview]
Message-ID: <878rxpiudp.fsf@codeaurora.org> (raw)
In-Reply-To: <20211026041616.4956-1-bqiang@codeaurora.org> (Baochen Qiang's message of "Tue, 26 Oct 2021 12:16:16 +0800")
Baochen Qiang <bqiang@codeaurora.org> writes:
> This patch set is to support one MSI vector for QCA6390.
>
> Depends-On:
> 1. ath11k: Fix crash caused by uninitialized TX ring
> https://patchwork.kernel.org/project/linux-wireless/patch/20211026011605.58615-1-quic_bqiang@quicinc.com/
>
> Baochen Qiang (1):
> ath11k: Set IRQ affinity to CPU0 in case of one MSI vector
>
> Carl Huang (6):
> ath11k: get msi_data again after request_irq is called
> ath11k: add CE and ext IRQ flag to indicate irq_handler
> ath11k: use ATH11K_PCI_IRQ_DP_OFFSET for DP IRQ
> ath11k: refactor multiple MSI vector implementation
> ath11k: supports one MSI vector
> ath11k: do not restore ASPM in case of single MSI vector
I assume this is v2 of Carl's patchset:
https://patchwork.kernel.org/project/linux-wireless/cover/20201223030225.2345-1-cjhuang@codeaurora.org/
Can you provide a changelog? No need to resend because of that, just a
reply to this thread enough.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-11-15 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 4:16 [PATCH 0/7] ath11k: support one MSI vector Baochen Qiang
2021-11-15 10:30 ` Kalle Valo [this message]
2021-11-16 2:50 ` Baochen Qiang
2021-11-19 12:31 ` Kalle Valo
2021-11-22 2:03 ` Baochen Qiang
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=878rxpiudp.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=bqiang@codeaurora.org \
--cc=linux-wireless@vger.kernel.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).