BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
	kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v3 0/7] Follow ups for verifier errors set
Date: Thu, 24 Sep 2026 21:10:07 +0000	[thread overview]
Message-ID: <179028420740.2201630.9968715215127891056.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924170646.2366016-1-memxor@gmail.com>

Hello:

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

On Thu, 24 Sep 2026 19:06:34 +0200 you wrote:
> Some follow up changes based on comments from Eduard, Sashiko, and BPF
> CI Bot. See commits for details.
> 
> Changelog:
> ----------
> v2 -> v3
> v2: https://lore.kernel.org/bpf/20260924092941.3174809-1-memxor@gmail.com
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/7] bpf: Correct verifier diagnostic attribution for stack reads
    https://git.kernel.org/bpf/bpf-next/c/9774ae5951c2
  - [bpf-next,v3,2/7] selftests/bpf: Test verifier stack-read diagnostic attribution
    https://git.kernel.org/bpf/bpf-next/c/e4b20ef33f93
  - [bpf-next,v3,3/7] bpf: Drop dead spill diagnostic condition
    https://git.kernel.org/bpf/bpf-next/c/e9ac05b98278
  - [bpf-next,v3,4/7] bpf: Report non-sleepable kfunc programs accurately
    https://git.kernel.org/bpf/bpf-next/c/dac3b7a30d7e
  - [bpf-next,v3,5/7] selftests/bpf: Test non-sleepable kfunc context
    (no matching commit)
  - [bpf-next,v3,6/7] bpf: Correct Program Structure diagnostic context
    (no matching commit)
  - [bpf-next,v3,7/7] selftests/bpf: Test Program Structure diagnostic context
    (no matching commit)

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-09-24 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 17:06 [PATCH bpf-next v3 0/7] Follow ups for verifier errors set Kumar Kartikeya Dwivedi
2026-09-24 17:06 ` [PATCH bpf-next v3 1/7] bpf: Correct verifier diagnostic attribution for stack reads Kumar Kartikeya Dwivedi
2026-09-24 17:06 ` [PATCH bpf-next v3 2/7] selftests/bpf: Test verifier stack-read diagnostic attribution Kumar Kartikeya Dwivedi
2026-09-24 17:06 ` [PATCH bpf-next v3 3/7] bpf: Drop dead spill diagnostic condition Kumar Kartikeya Dwivedi
2026-09-24 17:06 ` [PATCH bpf-next v3 4/7] bpf: Report non-sleepable kfunc programs accurately Kumar Kartikeya Dwivedi
2026-09-24 17:06 ` [PATCH bpf-next v3 5/7] selftests/bpf: Test non-sleepable kfunc context Kumar Kartikeya Dwivedi
2026-09-24 17:06 ` [PATCH bpf-next v3 6/7] bpf: Correct Program Structure diagnostic context Kumar Kartikeya Dwivedi
2026-09-24 17:06 ` [PATCH bpf-next v3 7/7] selftests/bpf: Test " Kumar Kartikeya Dwivedi
2026-09-24 21: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=179028420740.2201630.9968715215127891056.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=emil@etsalapatis.com \
    --cc=kernel-team@meta.com \
    --cc=kkd@meta.com \
    --cc=memxor@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