From: patchwork-bot+netdevbpf@kernel.org
To: Leon Hwang <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, memxor@gmail.com,
yepeilin@google.com, joshdon@google.com, brho@google.com,
kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Skip timer_interrupt case when bpf_timer is not supported
Date: Mon, 15 Sep 2025 17:30:06 +0000 [thread overview]
Message-ID: <175795740651.70512.4932386668355350266.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250915121657.28084-1-leon.hwang@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 15 Sep 2025 20:16:57 +0800 you wrote:
> Like commit fbdd61c94bcb ("selftests/bpf: Skip timer cases when bpf_timer is not supported"),
> 'timer_interrupt' test case should be skipped if verifier rejects
> bpf_timer with returning -EOPNOTSUPP.
>
> cd tools/testing/selftests/bpf
> ./test_progs -t timer
> 461 timer_interrupt:SKIP
> Summary: 6/0 PASSED, 7 SKIPPED, 0 FAILED
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Skip timer_interrupt case when bpf_timer is not supported
https://git.kernel.org/bpf/bpf-next/c/f7528e441213
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-09-15 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 12:16 [PATCH bpf-next] selftests/bpf: Skip timer_interrupt case when bpf_timer is not supported Leon Hwang
2025-09-15 17:30 ` 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=175795740651.70512.4932386668355350266.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brho@google.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=joshdon@google.com \
--cc=kernel-patches-bot@fb.com \
--cc=leon.hwang@linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=yepeilin@google.com \
--cc=yonghong.song@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 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.