From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: joyce.ooi@intel.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, robh@kernel.org, bhelgaas@google.com,
ley.foon.tan@intel.com, dinguyen@kernel.org,
Mahesh Vaidya <mahesh.vaidya@altera.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
subhransu.sekhar.prusty@altera.com, preetam.narayan@altera.com,
cheryl.bansal@altera.com, stable@vger.kernel.org
Subject: Re: [PATCH v2 0/2] PCI: altera: Fix IRQ cleanup on probe failure
Date: Fri, 15 May 2026 23:05:10 +0530 [thread overview]
Message-ID: <177886651035.12875.14264722458696413101.b4-ty@kernel.org> (raw)
In-Reply-To: <20260430204330.3121003-1-mahesh.vaidya@altera.com>
On Thu, 30 Apr 2026 13:43:28 -0700, Mahesh Vaidya wrote:
> This series addresses review feedback from v1 of the Altera PCIe probe
> failure cleanup fix.
>
> Patch 1 removes irq_dispose_mapping(pcie->irq) from the IRQ teardown
> path. pcie->irq is the parent IRQ returned by platform_get_irq(), not an
> IRQ created by the Altera INTx irq_domain, so the driver should detach
> the chained handler but not dispose the parent IRQ mapping.
>
> [...]
Applied, thanks!
[1/2] PCI: altera: Do not dispose parent IRQ mapping
commit: 5ef4bac02189bee0b7c170e352d7a38e13fe9678
[2/2] PCI: altera: Fix resource leaks on probe failure
commit: 7a94138caeb27f3c49c1dbd93bf422098925bb28
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2026-05-15 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 20:43 [PATCH v2 0/2] PCI: altera: Fix IRQ cleanup on probe failure Mahesh Vaidya
2026-04-30 20:43 ` [PATCH v2 1/2] PCI: altera: Do not dispose parent IRQ mapping Mahesh Vaidya
2026-04-30 20:43 ` [PATCH v2 2/2] PCI: altera: Fix resource leaks on probe failure Mahesh Vaidya
2026-05-15 17:35 ` Manivannan Sadhasivam [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=177886651035.12875.14264722458696413101.b4-ty@kernel.org \
--to=manivannan.sadhasivam@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=cheryl.bansal@altera.com \
--cc=dinguyen@kernel.org \
--cc=joyce.ooi@intel.com \
--cc=kwilczynski@kernel.org \
--cc=ley.foon.tan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mahesh.vaidya@altera.com \
--cc=preetam.narayan@altera.com \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=subhransu.sekhar.prusty@altera.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