From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, memxor@gmail.com, qmo@kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/6] bpftool, selftests: Add tests for C dump and fix a dropped type
Date: Sun, 30 Aug 2026 01:30:20 +0000 [thread overview]
Message-ID: <178805342039.3194634.18184271808930836434.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260828215207.3105313-1-ihor.solodrai@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 28 Aug 2026 14:52:01 -0700 you wrote:
> "bpftool btf dump format c" generates the vmlinux.h that BPF programs
> are built against, and it has no direct test coverage. Building
> against the header is not a substitute for testing it, nothing a
> compiler accepts would break the build.
>
> Add selftests targeting C dump in particular.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/6] selftests/bpf: Add compare_text_to_expected() helper
https://git.kernel.org/bpf/bpf-next/c/bd71904697c6
- [bpf-next,v2,2/6] selftests/bpf: Modernize btf_dump test scaffolding
https://git.kernel.org/bpf/bpf-next/c/c0722dc3288a
- [bpf-next,v2,3/6] selftests/bpf: Compare btf_dump expected output in-process
https://git.kernel.org/bpf/bpf-next/c/122255fb1933
- [bpf-next,v2,4/6] selftests/bpf: NUL-terminate bpftool command output
https://git.kernel.org/bpf/bpf-next/c/4f8a4c76f670
- [bpf-next,v2,5/6] selftests/bpf: Add tests for bpftool btf dump format c
https://git.kernel.org/bpf/bpf-next/c/438147f7f601
- [bpf-next,v2,6/6] bpftool: Don't drop a type in the sorted C dump
https://git.kernel.org/bpf/bpf-next/c/ff01f88a9136
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:[~2026-08-30 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 21:52 [PATCH bpf-next v2 0/6] bpftool, selftests: Add tests for C dump and fix a dropped type Ihor Solodrai
2026-08-28 21:52 ` [PATCH bpf-next v2 1/6] selftests/bpf: Add compare_text_to_expected() helper Ihor Solodrai
2026-08-28 21:52 ` [PATCH bpf-next v2 2/6] selftests/bpf: Modernize btf_dump test scaffolding Ihor Solodrai
2026-08-28 21:52 ` [PATCH bpf-next v2 3/6] selftests/bpf: Compare btf_dump expected output in-process Ihor Solodrai
2026-08-28 21:52 ` [PATCH bpf-next v2 4/6] selftests/bpf: NUL-terminate bpftool command output Ihor Solodrai
2026-08-28 21:52 ` [PATCH bpf-next v2 5/6] selftests/bpf: Add tests for bpftool btf dump format c Ihor Solodrai
2026-08-28 21:52 ` [PATCH bpf-next v2 6/6] bpftool: Don't drop a type in the sorted C dump Ihor Solodrai
2026-08-30 1: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=178805342039.3194634.18184271808930836434.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=ihor.solodrai@linux.dev \
--cc=memxor@gmail.com \
--cc=qmo@kernel.org \
/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.