From: Niklas Cassel <cassel@kernel.org>
To: Koichiro Den <den@valinux.co.jp>
Cc: mani@kernel.org, kwilczynski@kernel.org, kishon@kernel.org,
bhelgaas@google.com, jdmason@kudzu.us, dave.jiang@intel.com,
allenbh@gmail.com, Frank.Li@nxp.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, ntb@lists.linux.dev
Subject: Re: [PATCH 0/4] PCI: endpoint: Doorbell-related fixes
Date: Mon, 16 Feb 2026 12:51:23 +0100 [thread overview]
Message-ID: <aZMEu0_kAsRKOncz@ryzen> (raw)
In-Reply-To: <20260215150914.3392479-1-den@valinux.co.jp>
On Mon, Feb 16, 2026 at 12:09:10AM +0900, Koichiro Den wrote:
> Hi,
>
> This is a small fix-only series related to the previous (v6)
> doorbell-related series:
> https://lore.kernel.org/linux-pci/20260209125316.2132589-1-den@valinux.co.jp/
>
> These patches address a few independent fixes in pci-epf-vntb,
> pci-epf-test and pci-ep-msi:
>
> 1/4 fixes IRQ unwind in MSI doorbell setup (pci-epf-vntb)
> 2/4 adds a bounds check for doorbell BAR offset (pci-epf-test)
> 3/4 avoids free_irq() if doorbell IRQ was not successfully requested
> (pci-epf-test)
> 4/4 fixes error unwind and prevent double allocation in
> pci_epf_alloc_doorbell() (pci-ep-msi)
>
> These fixes were originally intended to be included in the next revision
> of the main series. However, doing so would have grown the v7 series to
> around 15 patches, so I am posting them separately to keep the feature
> series manageable.
I think it is a good idea to split out the doorbell fixes to its own series.
However, when splitting things out, it is getting a bit hard to track the
most "up to date" thing to look at.
At least for me, it would be nice if you could create a patchwork account
and then go in to:
https://patchwork.kernel.org/project/linux-pci/list/?submitter=216987
And mark your older series (that now has a newer version) as "Superseded".
You've been doing a lot of nice work lately, but it seems like the PCI
maintainers patchwork queue/backlog is quite large right now (7 long pages
in patchwork).
I think the chances are higher that your work will get picked up if you mark
your old series as "Superseeded", because it keeps the PCI maintainers queue/
backlog smaller. (So less chance that something will be overlooked/missed.)
(I do this myself too, because it seems to make things more likely to get
picked up.)
Kind regards,
Niklas
next prev parent reply other threads:[~2026-02-16 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 15:09 [PATCH 0/4] PCI: endpoint: Doorbell-related fixes Koichiro Den
2026-02-15 15:09 ` [PATCH 1/4] PCI: endpoint: pci-epf-vntb: Fix MSI doorbell IRQ unwind Koichiro Den
2026-02-16 11:56 ` Niklas Cassel
2026-02-16 14:02 ` Koichiro Den
2026-02-16 14:08 ` Niklas Cassel
2026-02-15 15:09 ` [PATCH 2/4] PCI: endpoint: pci-epf-test: Sanity-check doorbell offset within BAR Koichiro Den
2026-02-16 13:14 ` Niklas Cassel
2026-02-16 14:17 ` Koichiro Den
2026-02-15 15:09 ` [PATCH 3/4] PCI: endpoint: pci-epf-test: Don't free doorbell IRQ unless requested Koichiro Den
2026-02-16 11:35 ` Niklas Cassel
2026-02-16 14:30 ` Koichiro Den
2026-02-17 2:49 ` Koichiro Den
2026-02-15 15:09 ` [PATCH 4/4] PCI: endpoint: pci-ep-msi: Fix error unwind and prevent double alloc Koichiro Den
2026-02-16 11:57 ` Niklas Cassel
2026-02-16 11:51 ` Niklas Cassel [this message]
2026-02-16 13:48 ` [PATCH 0/4] PCI: endpoint: Doorbell-related fixes Koichiro Den
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=aZMEu0_kAsRKOncz@ryzen \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=allenbh@gmail.com \
--cc=bhelgaas@google.com \
--cc=dave.jiang@intel.com \
--cc=den@valinux.co.jp \
--cc=jdmason@kudzu.us \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@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