linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
	kafai@fb.com, eddyz87@gmail.com, songliubraving@fb.com,
	yhs@fb.com, john.fastabend@gmail.com, haoluo@google.com
Subject: Re: [PATCH bpf 1/3] selftests/bpf: Fix open-coded gettid syscall in uprobe syscall tests
Date: Wed, 01 Oct 2025 14:00:09 +0000	[thread overview]
Message-ID: <175932720902.2480904.3873827864966013132.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251001122223.170830-1-jolsa@kernel.org>

Hello:

This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed,  1 Oct 2025 14:22:21 +0200 you wrote:
> Commit 0e2fb011a0ba ("selftests/bpf: Clean up open-coded gettid syscall
> invocations") addressed the issue that older libc may not have a gettid()
> function call wrapper for the associated syscall.
> 
> The uprobe syscall tests got in from tip tree, using sys_gettid in there.
> 
> Fixes: 0e2fb011a0ba ("selftests/bpf: Clean up open-coded gettid syscall invocations")
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> 
> [...]

Here is the summary with links:
  - [bpf,1/3] selftests/bpf: Fix open-coded gettid syscall in uprobe syscall tests
    https://git.kernel.org/bpf/bpf/c/716d7388d3e7
  - [bpf,2/3] selftests/bpf: Fix typo in subtest_basic_usdt after merge conflict
    https://git.kernel.org/bpf/bpf/c/a5f5869dc234
  - [bpf,3/3] selftests/bpf: Fix realloc size in bpf_get_addrs
    https://git.kernel.org/bpf/bpf/c/4b946f6bb7d6

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



      parent reply	other threads:[~2025-10-01 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01 12:22 [PATCH bpf 1/3] selftests/bpf: Fix open-coded gettid syscall in uprobe syscall tests Jiri Olsa
2025-10-01 12:22 ` [PATCH bpf 2/3] selftests/bpf: Fix typo in subtest_basic_usdt after merge conflict Jiri Olsa
2025-10-01 12:22 ` [PATCH bpf 3/3] selftests/bpf: Fix realloc size in bpf_get_addrs Jiri Olsa
2025-10-01 14: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=175932720902.2480904.3873827864966013132.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=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).