All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuba Pawlak <kuba.pawlak@canonical.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, shuah@kernel.org, kuniyu@amazon.com,
	223556219+Copilot@users.noreply.github.com
Subject: Re: [PATCH net-next] selftests: net: Skip so_incoming_cpu on single-CPU systems
Date: Wed, 09 Sep 2026 21:00:13 +0000	[thread overview]
Message-ID: <178898761388.1057294.11276388701739327650.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904140334.562593-1-kuba.pawlak@canonical.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  4 Sep 2026 16:03:34 +0200 you wrote:
> The test requires at least two CPUs to exercise the distribution of
> connections between per-CPU listeners.  It currently enforces this
> prerequisite with an assertion, causing all test cases to fail on
> single-vCPU systems even though no kernel functionality was tested.
> 
> Report the unsupported environment as a skip instead.  Check the
> prerequisite before setting up the network namespace so skipped tests do
> not make unnecessary system changes.
> 
> [...]

Here is the summary with links:
  - [net-next] selftests: net: Skip so_incoming_cpu on single-CPU systems
    https://git.kernel.org/netdev/net-next/c/5bb36cd12006

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-09 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 14:03 [PATCH net-next] selftests: net: Skip so_incoming_cpu on single-CPU systems Kuba Pawlak
2026-09-09 17:03 ` netdev-bot+sashiko
2026-09-09 21:00 ` patchwork-bot+netdevbpf [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=178898761388.1057294.11276388701739327650.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=223556219+Copilot@users.noreply.github.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba.pawlak@canonical.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.