All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sun Jian <sun.jian.kdev@gmail.com>
Cc: andrii@kernel.org, shuah@kernel.org, eddyz87@gmail.com,
	ast@kernel.org, daniel@iogearbox.net, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] selftests/bpf: fix bpf_cookie failures
Date: Thu, 05 Mar 2026 23:10:12 +0000	[thread overview]
Message-ID: <177275221255.3320727.6349301821232758944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260228074555.122950-1-sun.jian.kdev@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Sat, 28 Feb 2026 15:45:53 +0800 you wrote:
> Fix bpf_cookie failures due to missing bpf_testmod and flaky perf_event
> triggering.
> 
> Tested:
>   ./test_progs -t bpf_cookie/perf_event -vv (30 runs): 0 failures
>   ./test_progs -t bpf_cookie -vv
> 
> [...]

Here is the summary with links:
  - [v2,1/2] selftests/bpf: bpf_cookie: skip kprobe_multi tests without bpf_testmod
    https://git.kernel.org/bpf/bpf-next/c/74d3305e620b
  - [v2,2/2] selftests/bpf: bpf_cookie: make perf_event subtest trigger reliably
    https://git.kernel.org/bpf/bpf-next/c/7f20d371fd87

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-03-05 23:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28  7:45 [PATCH v2 0/2] selftests/bpf: fix bpf_cookie failures Sun Jian
2026-02-28  7:45 ` [PATCH v2 1/2] selftests/bpf: bpf_cookie: skip kprobe_multi tests without bpf_testmod Sun Jian
2026-03-02 10:02   ` Jiri Olsa
2026-02-28  7:45 ` [PATCH v2 2/2] selftests/bpf: bpf_cookie: make perf_event subtest trigger reliably Sun Jian
2026-03-02 10:02   ` Jiri Olsa
2026-03-03  2:15     ` sun jian
2026-03-03 21:32       ` Jiri Olsa
2026-03-05 23:10 ` 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=177275221255.3320727.6349301821232758944.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=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=sun.jian.kdev@gmail.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 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.