Re: [PATCH bpf-next v3 0/4] bpf: replace min/max fields with struct cnum{32,64}

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 24 Apr 2026 15:52:41 -0700 you wrote:
> This RFC replaces s64, u64, s32, u32 scalar range domains tracked by
> verifier by a pair of circular numbers (cnums): one for 64-bit domain
> and another for 32-bit domain. Each cnum represents a range as a
> single arc on the circular number line, from which signed and unsigned
> bounds are derived on demand. See also wrapped intervals
> representation as in [1].
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/4] bpf: representation and basic operations on circular numbers
    https://git.kernel.org/bpf/bpf-next/c/256f0071f9b6
  - [bpf-next,v3,2/4] bpf: use accessor functions for bpf_reg_state min/max fields
    https://git.kernel.org/bpf/bpf-next/c/b93f7180f0bc
  - [bpf-next,v3,3/4] bpf: replace min/max fields with struct cnum{32,64}
    https://git.kernel.org/bpf/bpf-next/c/bbc631085503
  - [bpf-next,v3,4/4] selftests/bpf: new cases handled by 32->64 range refinements
    https://git.kernel.org/bpf/bpf-next/c/4c0710ab011e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html