From: patchwork-bot+netdevbpf@kernel.org
To: Josef Bacik <josef@toxicpanda.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v6 0/3] libbpf/bpftool: support merging split BTFs
Date: Thu, 05 Mar 2026 23:10:13 +0000 [thread overview]
Message-ID: <177275221379.3320727.2575476531046874927.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1772657690.git.josef@toxicpanda.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 4 Mar 2026 15:56:49 -0500 you wrote:
> v1: https://lore.kernel.org/bpf/cover.1771605821.git.josef@toxicpanda.com/
> v2: https://lore.kernel.org/bpf/cover.1771616227.git.josef@toxicpanda.com/
> v3: https://lore.kernel.org/bpf/cover.1771622266.git.josef@toxicpanda.com/
> v4: https://lore.kernel.org/bpf/cover.1771625484.git.josef@toxicpanda.com/
> v5: https://lore.kernel.org/bpf/cover.1771950922.git.josef@toxicpanda.com/
>
> v1->v2:
> - Added a btf__dedup() call to btf__add_btf() to ensure that we don't have
> duplicate types in the merged BTF.
> v2->v3:
> - AI review got confused about the UAF comment, so the comment was expanded to
> clarify the UAF potential.
> - Fixed potential clobbering of errno in the error path.
> v3->v4:
> - Fixed a potential silent corruption pointed out by the AI review bot.
> v4->v5:
> - Addressed Andrii's comments for 1/3.
> - Addressed Alan and Quentin's comments for 2/3.
> - Addressed Alan's comments for 3/3.
> - Added my Signed-off-by for the third patch.
> - Made sure to validate everything still worked.
> v5->v6:
> - Fixed the missed is_prefix comment.
> - Fixed the removed warning about skipping vmlinux.
>
> [...]
Here is the summary with links:
- [v6,1/3] libbpf: support appending split BTF in btf__add_btf()
(no matching commit)
- [v6,2/3] bpftool: support merging multiple module BTFs in btf dump
(no matching commit)
- [v6,3/3] selftests/bpf: add test for btf__add_btf() with split BTF sources
https://git.kernel.org/bpf/bpf-next/c/fefeeec61235
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-03-05 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 20:56 [PATCH v6 0/3] libbpf/bpftool: support merging split BTFs Josef Bacik
2026-03-04 20:56 ` [PATCH v6 1/3] libbpf: support appending split BTF in btf__add_btf() Josef Bacik
2026-03-04 22:12 ` Alan Maguire
2026-03-05 23:06 ` Andrii Nakryiko
2026-03-04 20:56 ` [PATCH v6 2/3] bpftool: support merging multiple module BTFs in btf dump Josef Bacik
2026-03-04 22:19 ` Alan Maguire
2026-03-05 23:06 ` Andrii Nakryiko
2026-03-04 20:56 ` [PATCH v6 3/3] selftests/bpf: add test for btf__add_btf() with split BTF sources Josef Bacik
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=177275221379.3320727.2575476531046874927.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=josef@toxicpanda.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.