From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
alexei.starovoitov@gmail.com, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/2] bpf: Emit struct bpf_xdp_sock type in vmlinux BTF
Date: Thu, 25 Sep 2025 21:40:08 +0000 [thread overview]
Message-ID: <175883640801.3525190.13922850394504839816.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250925170013.1752561-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 25 Sep 2025 10:00:12 -0700 you wrote:
> Similar to other BPF UAPI struct, force emit BTF of struct bpf_xdp_sock
> so that it is defined in vmlinux.h.
>
> In a later patch, a selftest will use vmlinux.h to get the definition of
> struct bpf_xdp_sock instead of bpf.h.
>
> Signed-off-by: Amery Hung <ameryhung@gmail.com>
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Emit struct bpf_xdp_sock type in vmlinux BTF
https://git.kernel.org/bpf/bpf-next/c/bc8712f2b525
- [bpf-next,2/2] selftests/bpf: Test changing packet data from global functions with a kfunc
https://git.kernel.org/bpf/bpf-next/c/9b5c111c3cd6
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:[~2025-09-25 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 17:00 [PATCH bpf-next 1/2] bpf: Emit struct bpf_xdp_sock type in vmlinux BTF Amery Hung
2025-09-25 17:00 ` [PATCH bpf-next 2/2] selftests/bpf: Test changing packet data from global functions with a kfunc Amery Hung
2025-09-25 21:58 ` Martin KaFai Lau
2025-09-25 23:16 ` Amery Hung
2025-09-25 21:40 ` 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=175883640801.3525190.13922850394504839816.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
/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.