From: patchwork-bot+netdevbpf@kernel.org
To: Yazhou Tang <tangyazhou@zju.edu.cn>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, tangyazhou518@outlook.com,
shenghaoyuan0928@163.com, ziye@zju.edu.cn
Subject: Re: [PATCH bpf-next v5 0/2] bpf: Add range tracking for BPF_DIV and BPF_MOD
Date: Wed, 21 Jan 2026 00:50:07 +0000 [thread overview]
Message-ID: <176895660735.669085.547201918994205516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260119085458.182221-1-tangyazhou@zju.edu.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 19 Jan 2026 16:54:56 +0800 you wrote:
> From: Yazhou Tang <tangyazhou518@outlook.com>
>
> Add range tracking (interval analysis) for BPF_DIV and BPF_MOD when
> divisor is constant. Please see commit log of 1/2 for more details.
>
> ---
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/2] bpf: Add range tracking for BPF_DIV and BPF_MOD
https://git.kernel.org/bpf/bpf-next/c/44fdd581d273
- [bpf-next,v5,2/2] selftests/bpf: Add tests for BPF_DIV and BPF_MOD range tracking
https://git.kernel.org/bpf/bpf-next/c/c9e440bf25a7
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-01-21 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 8:54 [PATCH bpf-next v5 0/2] bpf: Add range tracking for BPF_DIV and BPF_MOD Yazhou Tang
2026-01-19 8:54 ` [PATCH bpf-next v5 1/2] " Yazhou Tang
2026-01-20 18:51 ` Eduard Zingerman
2026-01-20 21:03 ` Alexei Starovoitov
2026-01-20 21:54 ` Eduard Zingerman
2026-01-20 22:02 ` Alexei Starovoitov
2026-01-21 0:32 ` Eduard Zingerman
2026-01-19 8:54 ` [PATCH bpf-next v5 2/2] selftests/bpf: Add tests for BPF_DIV and BPF_MOD range tracking Yazhou Tang
2026-01-21 0:50 ` 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=176895660735.669085.547201918994205516.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shenghaoyuan0928@163.com \
--cc=song@kernel.org \
--cc=tangyazhou518@outlook.com \
--cc=tangyazhou@zju.edu.cn \
--cc=yonghong.song@linux.dev \
--cc=ziye@zju.edu.cn \
/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