From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Aaradhana Sahu <aaradhana.sahu@oss.qualcomm.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, jjohnson@kernel.org,
quic_kiranv@quicinc.com,
vasanthakumar.thiagarajan@oss.qualcomm.com
Subject: Re: [PATCH ath-next v2 0/2] wifi: ath12k: Fix IRQ cleanup on PCI IRQ configuration failure
Date: Wed, 19 Aug 2026 19:18:44 +0800 [thread overview]
Message-ID: <25c3101a-294a-477d-979d-423e532cc6a5@oss.qualcomm.com> (raw)
In-Reply-To: <20260819110215.2485514-1-aaradhana.sahu@oss.qualcomm.com>
On 8/19/2026 7:02 PM, Aaradhana Sahu wrote:
> Free partially allocated IRQ resources when PCI IRQ configuration fails.
>
> The first patch frees previously requested CE IRQs if CE IRQ configuration
> fails.
>
> The second patch frees previously requested external IRQs, stores the IRQ
> number only after request_irq() succeeds, and cleans up allocated
> resources on failure.
>
> ---
> v2:
> -Used ath12k_pci_free_ce_irq() in the external IRQ config failure path.
> ---
>
> Aaradhana Sahu (2):
> wifi: ath12k: Free allocated CE IRQs on request_irq() failure
> wifi: ath12k: Free allocated external IRQs on request_irq() failure
>
> drivers/net/wireless/ath/ath12k/pci.c | 55 ++++++++++++++++-----------
> 1 file changed, 32 insertions(+), 23 deletions(-)
>
>
> base-commit: e07447e654476262558bee570f4cf456e2b32565
Reviewed-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
next prev parent reply other threads:[~2026-08-19 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 11:02 [PATCH ath-next v2 0/2] wifi: ath12k: Fix IRQ cleanup on PCI IRQ configuration failure Aaradhana Sahu
2026-08-19 11:02 ` [PATCH ath-next v2 1/2] wifi: ath12k: Free allocated CE IRQs on request_irq() failure Aaradhana Sahu
2026-08-19 11:02 ` [PATCH ath-next v2 2/2] wifi: ath12k: Free allocated external " Aaradhana Sahu
2026-08-19 11:18 ` Baochen Qiang [this message]
2026-08-19 15:13 ` [PATCH ath-next v2 0/2] wifi: ath12k: Fix IRQ cleanup on PCI IRQ configuration failure Rameshkumar Sundaram
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=25c3101a-294a-477d-979d-423e532cc6a5@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=aaradhana.sahu@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_kiranv@quicinc.com \
--cc=vasanthakumar.thiagarajan@oss.qualcomm.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