From: patchwork-bot+netdevbpf@kernel.org
To: Antoine Tenart <atenart@kernel.org>
Cc: andrii@kernel.org, eddyz87@gmail.com, bpf@vger.kernel.org,
paulhoussel2@gmail.com, alan.maguire@oracle.com
Subject: Re: [PATCH bpf v2 1/2] libbpf: fix deduplication of typedef with base definitions
Date: Wed, 22 Apr 2026 21:20:08 +0000 [thread overview]
Message-ID: <177689280832.4040916.15269160320880604899.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260417083319.32716-1-atenart@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 17 Apr 2026 10:33:17 +0200 you wrote:
> When deduplicating definitions for a module, typedef defined in the base
> are not removed. This is because the hash used for base types differs
> from the one used in the deduplication logic in btf_dedup_struct_type.
>
> This was introduced by the referenced commit when moving the typedef
> deduplication logic handling from btf_dedup_ref_type to
> btf_dedup_struct_type, as this also changed the hash logic
> (btf_hash_common to btf_hash_typedef).
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] libbpf: fix deduplication of typedef with base definitions
https://git.kernel.org/bpf/bpf-next/c/0831b110eb45
- [bpf,v2,2/2] selftests/bpf: ensure typedef are deduplicated in split BTF
https://git.kernel.org/bpf/bpf-next/c/1980023d759d
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-04-22 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 8:33 [PATCH bpf v2 1/2] libbpf: fix deduplication of typedef with base definitions Antoine Tenart
2026-04-17 8:33 ` [PATCH bpf v2 2/2] selftests/bpf: ensure typedef are deduplicated in split BTF Antoine Tenart
2026-04-17 22:10 ` [PATCH bpf v2 1/2] libbpf: fix deduplication of typedef with base definitions Alan Maguire
2026-04-22 21:20 ` 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=177689280832.4040916.15269160320880604899.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=atenart@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=paulhoussel2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox