From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, fsverity@lists.linux.dev,
andrii@kernel.org, jolsa@kernel.org,
linux-kbuild@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
netdev@vger.kernel.org, olsajiri@gmail.com,
quentin@isovalent.com, alan.maguire@oracle.com, acme@kernel.org,
eddyz87@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v5 00/12] bpf: Support dumping kfunc prototypes from BTF
Date: Wed, 12 Jun 2024 18:10:31 +0000 [thread overview]
Message-ID: <171821583135.29771.8486292481897939634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1718207789.git.dxu@dxuuu.xyz>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 12 Jun 2024 09:58:24 -0600 you wrote:
> This patchset enables both detecting as well as dumping compilable
> prototypes for kfuncs.
>
> The first commit instructs pahole to DECL_TAG kfuncs when available.
> This requires v1.27 which was released on 6/11/24. With it, users will
> be able to look at BTF inside vmlinux (or modules) and check if the
> kfunc they want is available.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,01/12] kbuild: bpf: Tell pahole to DECL_TAG kfuncs
https://git.kernel.org/bpf/bpf-next/c/ebb79e96f1ea
- [bpf-next,v5,02/12] bpf: selftests: Fix bpf_iter_task_vma_new() prototype
https://git.kernel.org/bpf/bpf-next/c/718135f5bd24
- [bpf-next,v5,03/12] bpf: selftests: Fix fentry test kfunc prototypes
https://git.kernel.org/bpf/bpf-next/c/dff96e4f5078
- [bpf-next,v5,04/12] bpf: selftests: Fix bpf_cpumask_first_zero() kfunc prototype
https://git.kernel.org/bpf/bpf-next/c/89f0b1abac49
- [bpf-next,v5,05/12] bpf: selftests: Fix bpf_map_sum_elem_count() kfunc prototype
https://git.kernel.org/bpf/bpf-next/c/ac42f636dc11
- [bpf-next,v5,06/12] bpf: Make bpf_session_cookie() kfunc return long *
https://git.kernel.org/bpf/bpf-next/c/2b8dd87332cd
- [bpf-next,v5,07/12] bpf: selftests: Namespace struct_opt callbacks in bpf_dctcp
https://git.kernel.org/bpf/bpf-next/c/0ce089cbdc6a
- [bpf-next,v5,08/12] bpf: verifier: Relax caller requirements for kfunc projection type args
https://git.kernel.org/bpf/bpf-next/c/ec209ad86324
- [bpf-next,v5,09/12] bpf: treewide: Align kfunc signatures to prog point-of-view
https://git.kernel.org/bpf/bpf-next/c/cce4c40b9606
- [bpf-next,v5,10/12] bpf: selftests: nf: Opt out of using generated kfunc prototypes
https://git.kernel.org/bpf/bpf-next/c/f709124dd72f
- [bpf-next,v5,11/12] bpf: selftests: xfrm: Opt out of using generated kfunc prototypes
https://git.kernel.org/bpf/bpf-next/c/c567cba34585
- [bpf-next,v5,12/12] bpftool: Support dumping kfunc prototypes from BTF
https://git.kernel.org/bpf/bpf-next/c/770abbb5a25a
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:[~2024-06-12 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 15:58 [PATCH bpf-next v5 00/12] bpf: Support dumping kfunc prototypes from BTF Daniel Xu
2024-06-12 15:58 ` [PATCH bpf-next v5 06/12] bpf: Make bpf_session_cookie() kfunc return long * Daniel Xu
2024-06-12 15:58 ` [PATCH bpf-next v5 09/12] bpf: treewide: Align kfunc signatures to prog point-of-view Daniel Xu
2024-06-12 18: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=171821583135.29771.8486292481897939634.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=eddyz87@gmail.com \
--cc=fsverity@lists.linux.dev \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=quentin@isovalent.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;
as well as URLs for NNTP newsgroup(s).