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, shuah@kernel.org, Frank.Li@nxp.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 3/3] selftests: pci_endpoint: Skip doorbell test when unsupported
Date: Mon, 16 Feb 2026 11:39:14 +0100 [thread overview]
Message-ID: <aZLz0pq6rJlDn-D3@ryzen> (raw)
In-Reply-To: <20260215150334.3391943-4-den@valinux.co.jp>
On Mon, Feb 16, 2026 at 12:03:34AM +0900, Koichiro Den wrote:
> PCITEST_DOORBELL may return -EOPNOTSUPP when the endpoint does not
> advertise CAP_DYNAMIC_INBOUND_MAPPING.
>
> Treat this like other optional capabilities and skip the doorbell test
> instead of reporting a failure.
>
> Suggested-by: Niklas Cassel <cassel@kernel.org>
> Signed-off-by: Koichiro Den <den@valinux.co.jp>
> ---
Reviewed-by: Niklas Cassel <cassel@kernel.org>
Thank you for doing this work!
next prev parent reply other threads:[~2026-02-16 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 15:03 [PATCH 0/3] PCI: endpoint tests: Make doorbell test capability-aware Koichiro Den
2026-02-15 15:03 ` [PATCH 1/3] PCI: endpoint: pci-epf-test: Advertise dynamic inbound mapping support Koichiro Den
2026-02-16 10:38 ` Niklas Cassel
2026-02-15 15:03 ` [PATCH 2/3] misc: pci_endpoint_test: Gate doorbell test on dynamic inbound mapping Koichiro Den
2026-02-16 10:38 ` Niklas Cassel
2026-02-15 15:03 ` [PATCH 3/3] selftests: pci_endpoint: Skip doorbell test when unsupported Koichiro Den
2026-02-16 10:39 ` Niklas Cassel [this message]
2026-02-24 10:32 ` [PATCH 0/3] PCI: endpoint tests: Make doorbell test capability-aware Manivannan Sadhasivam
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=aZLz0pq6rJlDn-D3@ryzen \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=den@valinux.co.jp \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=shuah@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