From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v2 0/7] bpf: follow-up for scalar evolution series
Date: Wed, 14 Oct 2026 22:30:06 +0000 [thread overview]
Message-ID: <179201700677.3065620.12309731207702632706.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013-scev-minimal-v3-followups-v2-0-6d9d61965486@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 13 Oct 2026 23:24:35 -0700 you wrote:
> Assorted follow-ups for the series [1]:
> - Handle ARG_SCALAR and ARG_PTR_TO_DYNPTR in
> bpf_global_subprog_stack_access_bytes().
> - Fixes for other nits reported by bots for the series.
>
> Changelog v1 -> v2:
> - dropped patch #1,
> "bpf: static subprogram arguments liveness should use BTF type info",
> see the v1 lore link for explanation.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/7] bpf: more precise stack liveness effects for global func params
https://git.kernel.org/bpf/bpf-next/c/e980770b431a
- [bpf-next,v2,2/7] bpf: avoid duplicate declaration for BPF_SCEV_REGS_NUM
https://git.kernel.org/bpf/bpf-next/c/06e0e41e6223
- [bpf-next,v2,3/7] bpf: reg_bounds_sync() comment fixup
https://git.kernel.org/bpf/bpf-next/c/4d274f1ef049
- [bpf-next,v2,4/7] selftests/bpf: stack effects of scalar/dynptr global subprog params
https://git.kernel.org/bpf/bpf-next/c/ff9e7261e0ce
- [bpf-next,v2,5/7] selftests/bpf: harden __msg pattern for global_callee_btf_arg
https://git.kernel.org/bpf/bpf-next/c/3f3137ef1c9e
- [bpf-next,v2,6/7] selftests/bpf: harden __msg patterns for step_movsx_bounds_on_line
https://git.kernel.org/bpf/bpf-next/c/1bb030a11fa6
- [bpf-next,v2,7/7] selftests/bpf: BPF_F_ANY_ALIGNMENT for byte_array_size_spanning()
https://git.kernel.org/bpf/bpf-next/c/75fc921e7f80
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-14 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 6:24 [PATCH bpf-next v2 0/7] bpf: follow-up for scalar evolution series Eduard Zingerman
2026-10-14 6:24 ` [PATCH bpf-next v2 1/7] bpf: more precise stack liveness effects for global func params Eduard Zingerman
2026-10-14 6:24 ` [PATCH bpf-next v2 2/7] bpf: avoid duplicate declaration for BPF_SCEV_REGS_NUM Eduard Zingerman
2026-10-14 6:24 ` [PATCH bpf-next v2 3/7] bpf: reg_bounds_sync() comment fixup Eduard Zingerman
2026-10-14 6:24 ` [PATCH bpf-next v2 4/7] selftests/bpf: stack effects of scalar/dynptr global subprog params Eduard Zingerman
2026-10-14 6:24 ` [PATCH bpf-next v2 5/7] selftests/bpf: harden __msg pattern for global_callee_btf_arg Eduard Zingerman
2026-10-14 6:24 ` [PATCH bpf-next v2 6/7] selftests/bpf: harden __msg patterns for step_movsx_bounds_on_line Eduard Zingerman
2026-10-14 6:37 ` sashiko-bot
2026-10-14 6:24 ` [PATCH bpf-next v2 7/7] selftests/bpf: BPF_F_ANY_ALIGNMENT for byte_array_size_spanning() Eduard Zingerman
2026-10-14 22:30 ` 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=179201700677.3065620.12309731207702632706.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