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, alan.maguire@oracle.com,
jolsa@kernel.org, emil@etsalapatis.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/6] resolve_btfids: Implement BTF tags emission for kfuncs
Date: Fri, 07 Aug 2026 05:10:14 +0000 [thread overview]
Message-ID: <178607941464.1610510.8127033300425733213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260807032029.78092-1-ihor.solodrai@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:
On Thu, 6 Aug 2026 20:20:23 -0700 you wrote:
> BTF data for the kernel is generated through the following pipeline:
> * DWARF is emitted by the compiler
> * pahole reads in DWARF and produces BTF
> * resolve_btfids makes kernel-specific btf2btf transformation and
> patches .BTF_ids section
>
> This is orchestrated by link-vmlinux.sh, gen-btf.sh and Makefile.btf
> in ./scripts directory.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/6] resolve_btfids: Deduplicate BTF after btf2btf transformations
https://git.kernel.org/bpf/bpf-next/c/3d72aca40b83
- [bpf-next,v3,2/6] resolve_btfids: Process KF_ARENA_* flags in resolve_btfids
https://git.kernel.org/bpf/bpf-next/c/27a78c2e7eee
- [bpf-next,v3,3/6] selftests/bpf: Verify arena type tags in resolve_btfids test
https://git.kernel.org/bpf/bpf-next/c/ef77140f4b3a
- [bpf-next,v3,4/6] resolve_btfids: Emit bpf_kfunc and bpf_fastcall decl tags
https://git.kernel.org/bpf/bpf-next/c/692393104909
- [bpf-next,v3,5/6] selftests/bpf: Verify decl tags emission in resolve_btfids test
https://git.kernel.org/bpf/bpf-next/c/9f3881ecad88
- [bpf-next,v3,6/6] docs, resolve_btfids: Document kfunc BTF annotation emission
https://git.kernel.org/bpf/bpf-next/c/fd5425b67355
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-07 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 3:20 [PATCH bpf-next v3 0/6] resolve_btfids: Implement BTF tags emission for kfuncs Ihor Solodrai
2026-08-07 3:20 ` [PATCH bpf-next v3 1/6] resolve_btfids: Deduplicate BTF after btf2btf transformations Ihor Solodrai
2026-08-07 3:20 ` [PATCH bpf-next v3 2/6] resolve_btfids: Process KF_ARENA_* flags in resolve_btfids Ihor Solodrai
2026-08-07 3:20 ` [PATCH bpf-next v3 3/6] selftests/bpf: Verify arena type tags in resolve_btfids test Ihor Solodrai
2026-08-07 3:20 ` [PATCH bpf-next v3 4/6] resolve_btfids: Emit bpf_kfunc and bpf_fastcall decl tags Ihor Solodrai
2026-08-07 3:20 ` [PATCH bpf-next v3 5/6] selftests/bpf: Verify decl tags emission in resolve_btfids test Ihor Solodrai
2026-08-07 4:38 ` bot+bpf-ci
2026-08-07 3:20 ` [PATCH bpf-next v3 6/6] docs, resolve_btfids: Document kfunc BTF annotation emission Ihor Solodrai
2026-08-07 4:38 ` bot+bpf-ci
2026-08-07 5: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=178607941464.1610510.8127033300425733213.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=memxor@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