From: patchwork-bot+netdevbpf@kernel.org
To: Hengqi Chen <hengqi.chen@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev
Subject: Re: [PATCH bpf-next v3] selftests/bpf: Use vmlinux.h for BPF programs
Date: Thu, 21 Aug 2025 18:50:06 +0000 [thread overview]
Message-ID: <175580220600.1148464.7863821287864768578.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250821030254.398826-1-hengqi.chen@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 21 Aug 2025 03:02:54 +0000 you wrote:
> Some of the bpf test progs still use linux/libc headers.
> Let's use vmlinux.h instead like the rest of test progs.
> This will also ease cross compiling.
>
> Signed-off-by: Hengqi Chen <hengqi.chen@gmail.com>
> ---
> tools/testing/selftests/bpf/progs/loop1.c | 7 +------
> tools/testing/selftests/bpf/progs/loop2.c | 7 +------
> tools/testing/selftests/bpf/progs/loop3.c | 7 +------
> tools/testing/selftests/bpf/progs/loop6.c | 21 +++++++------------
> .../selftests/bpf/progs/test_overhead.c | 5 +----
> 5 files changed, 11 insertions(+), 36 deletions(-)
Here is the summary with links:
- [bpf-next,v3] selftests/bpf: Use vmlinux.h for BPF programs
https://git.kernel.org/bpf/bpf-next/c/21aeabb68258
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-08-21 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 3:02 [PATCH bpf-next v3] selftests/bpf: Use vmlinux.h for BPF programs Hengqi Chen
2025-08-21 18: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=175580220600.1148464.7863821287864768578.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=hengqi.chen@gmail.com \
--cc=martin.lau@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.