mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
	leitao@debian.org, willemb@google.com, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: drv-net: netpoll_basic: xfail if no hits
Date: Sat, 21 Nov 2026 22:50:08 +0000	[thread overview]
Message-ID: <179530140827.1198296.16586810100867874440.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261119-net-next-netpoll-basic-xfail-v1-1-206bf59911ea@kernel.org>

Hello:

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

On Thu, 19 Nov 2026 11:52:01 +0100 you wrote:
> When netpoll_poll_dev() is not called during the test, bpftrace doesn't
> print the '@hits' map, because it is empty. The test then fails instead
> of reporting the expected XFAIL:
> 
>   net.lib.py.ksft.KsftFailEx: bpftrace failed to run!?: {}
> 
> This has been observed regularly in the netdev CI with netdevsim, since
> a recent switch to Fedora 45: hitting this function depends on timings.
> 
> [...]

Here is the summary with links:
  - [net-next] selftests: drv-net: netpoll_basic: xfail if no hits
    https://git.kernel.org/netdev/net-next/c/fd5f80a8a427

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-11-21 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 10:52 Matthieu Baerts (NGI0)
2026-11-20 18:41 ` Breno Leitao
2026-11-21 22:50 ` 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=179530140827.1198296.16586810100867874440.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=matttbe@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=willemb@google.com \
    /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®