BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, puranjay12@gmail.com, ast@kernel.org,
	andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, mykyta.yatsenko5@gmail.com,
	kernel-team@meta.com, andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next v3 0/5] bpf: verifier: Improve state pruning for scalar registers
Date: Tue, 03 Feb 2026 18:40:11 +0000	[thread overview]
Message-ID: <177014401163.1597022.5779253745242388746.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203165102.2302462-1-puranjay@kernel.org>

Hello:

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

On Tue,  3 Feb 2026 08:50:56 -0800 you wrote:
> V2: https://lore.kernel.org/all/20260203022229.1630849-1-puranjay@kernel.org/
> Changes in V3:
> - Fix spelling mistakes in commit logs (AI)
> - Fix an incorrect comment in the selftest added in patch 5 (AI)
> - Improve the title of patch 5
> 
> V1: https://lore.kernel.org/all/20260202104414.3103323-1-puranjay@kernel.org/
> Changes in V2:
> - Collected acked by Eduard
> - Removed some unnecessary comments
> - Added a selftest for id=0 equivalence in Patch 5
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/5] bpf: verifier: Assign ids on stack fills
    https://git.kernel.org/bpf/bpf-next/c/3cd5c890652b
  - [bpf-next,v3,2/5] bpf: verifier: Clear singular ids for scalars
    https://git.kernel.org/bpf/bpf-next/c/b2a0aa3a8739
  - [bpf-next,v3,3/5] bpf: verifier: Relax maybe_widen_reg() constraints
    (no matching commit)
  - [bpf-next,v3,4/5] bpf: verifier: Relax scalar id equivalence for state pruning
    https://git.kernel.org/bpf/bpf-next/c/b0388bafa494
  - [bpf-next,v3,5/5] selftests: bpf: verifier_scalar_ids: Add a test for ids=0
    https://git.kernel.org/bpf/bpf-next/c/f6ef5584ccb5

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-02-03 18:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 16:50 [PATCH bpf-next v3 0/5] bpf: verifier: Improve state pruning for scalar registers Puranjay Mohan
2026-02-03 16:50 ` [PATCH bpf-next v3 1/5] bpf: verifier: Assign ids on stack fills Puranjay Mohan
2026-02-03 16:50 ` [PATCH bpf-next v3 2/5] bpf: verifier: Clear singular ids for scalars Puranjay Mohan
2026-02-03 16:50 ` [PATCH bpf-next v3 3/5] bpf: verifier: Relax maybe_widen_reg() constraints Puranjay Mohan
2026-02-03 16:51 ` [PATCH bpf-next v3 4/5] bpf: verifier: Relax scalar id equivalence for state pruning Puranjay Mohan
2026-02-03 16:51 ` [PATCH bpf-next v3 5/5] selftests: bpf: verifier_scalar_ids: Add a test for ids=0 Puranjay Mohan
2026-02-03 18:40 ` 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=177014401163.1597022.5779253745242388746.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=puranjay12@gmail.com \
    --cc=puranjay@kernel.org \
    /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