From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v4 0/9] bpf: Follow up by-value struct and __int128 argument support
Date: Fri, 16 Oct 2026 20:00:07 +0000 [thread overview]
Message-ID: <179218080725.945731.309656099447652892.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016183039.1132126-1-yonghong.song@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 16 Oct 2026 11:30:39 -0700 you wrote:
> This is a follow-up to the series "bpf: Support by-value struct and
> __int128 arguments" [1], which placed kfunc arguments by the kernel
> calling convention in the x86-64 and arm64 JITs, and made the arm64
> trampoline place an argument aligned to 16 bytes: an __int128, or an
> aggregate holding one. This series covers what was left, and a few
> problems found on the way:
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/9] bpf, x86: Pass a trampoline's stack arguments by the calling convention
https://git.kernel.org/bpf/bpf-next/c/9f9c30435ca9
- [bpf-next,v4,2/9] selftests/bpf: Test trampoline stack args in a program that can tail call
https://git.kernel.org/bpf/bpf-next/c/6b26307ce697
- [bpf-next,v4,3/9] selftests/bpf: Test by-value __int128 kfunc arguments at an odd slot
https://git.kernel.org/bpf/bpf-next/c/98e46955064b
- [bpf-next,v4,4/9] bpf: Describe a BPF function to its trampoline as one u64 per slot
https://git.kernel.org/bpf/bpf-next/c/ab70d0d7f1b1
- [bpf-next,v4,5/9] bpf, x86: Place trampoline arguments by the x86-64 calling convention
https://git.kernel.org/bpf/bpf-next/c/0e6d7e9669be
- [bpf-next,v4,6/9] selftests/bpf: Test trampoline args around a 16-byte aligned stack arg
https://git.kernel.org/bpf/bpf-next/c/b68782116bfd
- [bpf-next,v4,7/9] selftests/bpf: Test trampoline args of a BPF function at an odd slot
https://git.kernel.org/bpf/bpf-next/c/9c6fc12a8e4e
- [bpf-next,v4,8/9] bpf: Refuse a trampoline on an unreliable static function with stack args
https://git.kernel.org/bpf/bpf-next/c/9b2e5136760a
- [bpf-next,v4,9/9] selftests/bpf: Test trampolines on more BPF functions with stack args
https://git.kernel.org/bpf/bpf-next/c/8395b4031881
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-10-16 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 18:30 [PATCH bpf-next v4 0/9] bpf: Follow up by-value struct and __int128 argument support Yonghong Song
2026-10-16 18:30 ` [PATCH bpf-next v4 1/9] bpf, x86: Pass a trampoline's stack arguments by the calling convention Yonghong Song
2026-10-16 18:30 ` [PATCH bpf-next v4 2/9] selftests/bpf: Test trampoline stack args in a program that can tail call Yonghong Song
2026-10-16 18:30 ` [PATCH bpf-next v4 3/9] selftests/bpf: Test by-value __int128 kfunc arguments at an odd slot Yonghong Song
2026-10-16 18:31 ` [PATCH bpf-next v4 4/9] bpf: Describe a BPF function to its trampoline as one u64 per slot Yonghong Song
2026-10-16 18:31 ` [PATCH bpf-next v4 5/9] bpf, x86: Place trampoline arguments by the x86-64 calling convention Yonghong Song
2026-10-16 18:31 ` [PATCH bpf-next v4 6/9] selftests/bpf: Test trampoline args around a 16-byte aligned stack arg Yonghong Song
2026-10-16 18:31 ` [PATCH bpf-next v4 7/9] selftests/bpf: Test trampoline args of a BPF function at an odd slot Yonghong Song
2026-10-16 18:31 ` [PATCH bpf-next v4 8/9] bpf: Refuse a trampoline on an unreliable static function with stack args Yonghong Song
2026-10-16 19:05 ` bot+bpf-ci
2026-10-16 18:31 ` [PATCH bpf-next v4 9/9] selftests/bpf: Test trampolines on more BPF functions " Yonghong Song
2026-10-16 20:00 ` 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=179218080725.945731.309656099447652892.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=yonghong.song@linux.dev \
/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