BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Paul Chaignon <paul.chaignon@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix test for refinement of single-value tnum
Date: Tue, 19 May 2026 02:10:09 +0000	[thread overview]
Message-ID: <177915660913.2054007.2673876026046526600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <be2dc2c3d85120286e60b3029b3338fff339f942.1779121582.git.paul.chaignon@gmail.com>

Hello:

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

On Mon, 18 May 2026 18:26:35 +0200 you wrote:
> This patch fixes the "bounds refinement with single-value tnum on umin"
> verifier selftest. This selftest was introduced in commit e6ad477d1bf8
> ("selftests/bpf: Test refinement of single-value tnum") to cover the
> logic from __update_reg64_bounds(), introduced in commit efc11a667878
> ("bpf: Improve bounds when tnum has a single possible value"). However,
> the test still passes if that last commit is reverted.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix test for refinement of single-value tnum
    https://git.kernel.org/bpf/bpf-next/c/523d2f42b406

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



      parent reply	other threads:[~2026-05-19  2:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 16:26 [PATCH bpf-next] selftests/bpf: Fix test for refinement of single-value tnum Paul Chaignon
2026-05-18 17:09 ` bot+bpf-ci
2026-05-18 17:32   ` Paul Chaignon
2026-05-19  2:10 ` 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=177915660913.2054007.2673876026046526600.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=memxor@gmail.com \
    --cc=paul.chaignon@gmail.com \
    /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