From: Cosmin Ratiu <cratiu@nvidia.com>
To: "kuba@kernel.org" <kuba@kernel.org>
Cc: "andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
Carolina Jubran <cjubran@nvidia.com>
Subject: Re: [PATCH net-next 2/2] selftests: drv-net: psp: Don't fail psp_responder when no PSP devs found
Date: Wed, 7 Jan 2026 11:47:43 +0000 [thread overview]
Message-ID: <4094f781edeb87b38594d54dbfeec674ebaf1b13.camel@nvidia.com> (raw)
In-Reply-To: <20260105175206.7b74067d@kernel.org>
On Mon, 2026-01-05 at 17:52 -0800, Jakub Kicinski wrote:
> On Mon, 5 Jan 2026 12:04:24 +0200 Cosmin Ratiu wrote:
>
> > Change psp_responder to open the server socket and listen for
> > control
> > connections normally, and leave the skipping of the various test
> > cases
> > which require a PSP device (~most, but not all of them) to the
> > parent
> > test. This results in output like:
> >
> > ok 1 psp.test_case # SKIP No PSP devices found
> > [...]
> > ok 12 psp.dev_get_device # SKIP No PSP devices found
> > ok 13 psp.dev_get_device_bad
> > ok 14 psp.dev_rotate # SKIP No PSP devices found
> > [...]
>
> To be clear - in this case the DUT also doesn't have a PSP device?
> I'm struggling to connect the dots on how this error msg could come
> from psp_responder.
This happens when one runs the psp selftest against a DUT with PSP
disabled (e.g. no PSP devices present, or cap bits off or something
else not working).
This patch makes psp_responder not fail in this case, establish the
control connection and let the parent test determine which test cases
to run.
Cosmin.
prev parent reply other threads:[~2026-01-07 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 10:04 [PATCH net-next 0/2] PSP self test improvements Cosmin Ratiu
2026-01-05 10:04 ` [PATCH net-next 1/2] selftests: drv-net: psp: Use first device when multiple are present Cosmin Ratiu
2026-01-06 1:44 ` Jakub Kicinski
2026-01-07 11:44 ` Cosmin Ratiu
2026-01-05 10:04 ` [PATCH net-next 2/2] selftests: drv-net: psp: Don't fail psp_responder when no PSP devs found Cosmin Ratiu
2026-01-06 1:52 ` Jakub Kicinski
2026-01-07 11:47 ` Cosmin Ratiu [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=4094f781edeb87b38594d54dbfeec674ebaf1b13.camel@nvidia.com \
--to=cratiu@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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