BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Maxim Khmelevskii <max@linux.ibm.com>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	bpf@vger.kernel.org, iii@linux.ibm.com, hca@linux.ibm.com,
	gor@linux.ibm.com, agordeev@linux.ibm.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Skip res_spin_lock_stress if no perf support
Date: Wed, 08 Jul 2026 20:00:06 +0000	[thread overview]
Message-ID: <178354080689.3087685.11132788742995671066.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708104729.1248234-2-max@linux.ibm.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Wed,  8 Jul 2026 12:47:17 +0200 you wrote:
> Probe PMU support before loading bpf_test_rqspinlock.ko,
> otherwise the test fails with not obvious error without
> proper perf event support:
> 
>     Failed to load bpf_test_rqspinlock.ko into the kernel: -2
>     serial_test_res_spin_lock_stress:FAIL:load module AA
>         unexpected error: -22 (errno 2)
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Skip res_spin_lock_stress if no perf support
    https://git.kernel.org/bpf/bpf-next/c/41ec7e4a1779

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



      reply	other threads:[~2026-07-08 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 10:47 [PATCH bpf-next] selftests/bpf: Skip res_spin_lock_stress if no perf support Maxim Khmelevskii
2026-07-08 20: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=178354080689.3087685.11132788742995671066.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=max@linux.ibm.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