From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: Jon Mason <jdmason@kudzu.us>, Dave Jiang <dave.jiang@intel.com>,
Allen Hubbe <allenbh@gmail.com>,
Jerome Brunet <jbrunet@baylibre.com>, Frank Li <Frank.Li@nxp.com>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Koichiro Den <den@valinux.co.jp>
Cc: ntb@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] NTB: epf: Fix ntb_hw_epf ISR issues
Date: Wed, 27 May 2026 10:06:48 +0200 [thread overview]
Message-ID: <177986920811.9478.5259181719424630932.b4-ty@b4> (raw)
In-Reply-To: <20260304083028.1391068-1-den@valinux.co.jp>
On Wed, 04 Mar 2026 17:30:26 +0900, Koichiro Den wrote:
> ntb_hw_epf handles doorbell interrupts using multiple MSI/MSI-X vectors.
> This small patch series is to address two issues in the interrupt
> setup/handler path:
>
> 1) ntb_epf_init_isr() does not unwind already requested IRQs when
> request_irq() fails part-way through the vector loop.
>
> [...]
Applied, thanks!
[1/2] NTB: epf: Fix request_irq() unwind in ntb_epf_init_isr()
commit: 9f67debe71a1ac6430ef8bdd8e1b8ab39942e63c
[2/2] NTB: epf: Avoid pci_irq_vector() from hardirq context
commit: 9985e6ea0c227de2027210dc45dfc33139203f72
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2026-05-27 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 8:30 Koichiro Den
2026-03-04 8:30 ` [PATCH 1/2] NTB: epf: Fix request_irq() unwind in ntb_epf_init_isr() Koichiro Den
2026-03-04 8:30 ` [PATCH 2/2] NTB: epf: Avoid pci_irq_vector() from hardirq context Koichiro Den
2026-03-17 3:01 ` [PATCH 0/2] NTB: epf: Fix ntb_hw_epf ISR issues Koichiro Den
2026-03-18 19:51 ` Dave Jiang
2026-05-27 8:06 ` 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=177986920811.9478.5259181719424630932.b4-ty@b4 \
--to=manivannan.sadhasivam@oss.qualcomm.com \
--cc=Frank.Li@nxp.com \
--cc=allenbh@gmail.com \
--cc=bhelgaas@google.com \
--cc=dave.jiang@intel.com \
--cc=den@valinux.co.jp \
--cc=jbrunet@baylibre.com \
--cc=jdmason@kudzu.us \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=ntb@lists.linux.dev \
/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
all inboxes | Powered by JetHome®