From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-trace-kernel@vger.kernel.org, coreteam@netfilter.org,
bpf@vger.kernel.org, linux-input@vger.kernel.org,
cgroups@vger.kernel.org, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
fsverity@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
netfilter-devel@vger.kernel.org, alexei.starovoitov@gmail.com,
olsajiri@gmail.com, quentin@isovalent.com,
alan.maguire@oracle.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next v4 0/3] Annotate kfuncs in .BTF_ids section
Date: Wed, 31 Jan 2024 20:20:28 +0000 [thread overview]
Message-ID: <170673242899.4502.6917209613478941432.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1706491398.git.dxu@dxuuu.xyz>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 28 Jan 2024 18:24:05 -0700 you wrote:
> === Description ===
>
> This is a bpf-treewide change that annotates all kfuncs as such inside
> .BTF_ids. This annotation eventually allows us to automatically generate
> kfunc prototypes from bpftool.
>
> We store this metadata inside a yet-unused flags field inside struct
> btf_id_set8 (thanks Kumar!). pahole will be taught where to look.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/3] bpf: btf: Support flags for BTF_SET8 sets
https://git.kernel.org/bpf/bpf-next/c/79b47344bbc5
- [bpf-next,v4,2/3] bpf: btf: Add BTF_KFUNCS_START/END macro pair
https://git.kernel.org/bpf/bpf-next/c/2747e0ee57c2
- [bpf-next,v4,3/3] bpf: treewide: Annotate BPF kfuncs in BTF
https://git.kernel.org/bpf/bpf-next/c/6e7769e6419f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-trace-kernel@vger.kernel.org, coreteam@netfilter.org,
bpf@vger.kernel.org, linux-input@vger.kernel.org,
cgroups@vger.kernel.org, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
fsverity@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
netfilter-devel@vger.kernel.org, alexei.starovoitov@gmail.com,
olsajiri@gmail.com, quentin@isovalent.com,
alan.maguire@oracle.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next v4 0/3] Annotate kfuncs in .BTF_ids section
Date: Wed, 31 Jan 2024 20:20:28 +0000 [thread overview]
Message-ID: <170673242899.4502.6917209613478941432.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1706491398.git.dxu@dxuuu.xyz>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 28 Jan 2024 18:24:05 -0700 you wrote:
> === Description ===
>
> This is a bpf-treewide change that annotates all kfuncs as such inside
> .BTF_ids. This annotation eventually allows us to automatically generate
> kfunc prototypes from bpftool.
>
> We store this metadata inside a yet-unused flags field inside struct
> btf_id_set8 (thanks Kumar!). pahole will be taught where to look.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/3] bpf: btf: Support flags for BTF_SET8 sets
https://git.kernel.org/bpf/bpf-next/c/79b47344bbc5
- [bpf-next,v4,2/3] bpf: btf: Add BTF_KFUNCS_START/END macro pair
https://git.kernel.org/bpf/bpf-next/c/2747e0ee57c2
- [bpf-next,v4,3/3] bpf: treewide: Annotate BPF kfuncs in BTF
https://git.kernel.org/bpf/bpf-next/c/6e7769e6419f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-31 20:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 1:24 [PATCH bpf-next v4 0/3] Annotate kfuncs in .BTF_ids section Daniel Xu
2024-01-29 1:24 ` Daniel Xu
2024-01-29 1:24 ` [PATCH bpf-next v4 1/3] bpf: btf: Support flags for BTF_SET8 sets Daniel Xu
2024-01-29 1:24 ` [PATCH bpf-next v4 2/3] bpf: btf: Add BTF_KFUNCS_START/END macro pair Daniel Xu
2024-01-29 1:24 ` [PATCH bpf-next v4 3/3] bpf: treewide: Annotate BPF kfuncs in BTF Daniel Xu
2024-01-31 9:24 ` Benjamin Tissoires
2024-02-05 2:41 ` kernel test robot
2024-01-31 9:47 ` [PATCH bpf-next v4 0/3] Annotate kfuncs in .BTF_ids section Jiri Olsa
2024-01-31 9:47 ` Jiri Olsa
2024-01-31 20:20 ` patchwork-bot+netdevbpf [this message]
2024-01-31 20:20 ` patchwork-bot+netdevbpf
2024-02-02 23:09 ` Manu Bretelle
2024-02-02 23:09 ` Manu Bretelle
2024-02-03 1:34 ` Daniel Xu
2024-02-03 1:34 ` Daniel Xu
2024-02-03 14:40 ` Jiri Olsa
2024-02-03 14:40 ` Jiri Olsa
2024-02-03 18:45 ` Manu Bretelle
2024-02-03 18:45 ` Manu Bretelle
2024-02-05 18:43 ` Viktor Malik
2024-02-05 18:43 ` Viktor Malik
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=170673242899.4502.6917209613478941432.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=coreteam@netfilter.org \
--cc=dxu@dxuuu.xyz \
--cc=fsverity@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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 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.