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 v1 0/2] Open up res_spin_lock() in all contexts
Date: Mon, 27 Jul 2026 22:50:07 +0000	[thread overview]
Message-ID: <178519260713.1445878.13477862582196438048.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260724201634.3025247-1-memxor@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Fri, 24 Jul 2026 22:16:30 +0200 you wrote:
> Spin off first patch with added tests from [0]. See commits for details.
> 
>   [0]: https://lore.kernel.org/bpf/20260719113551.1294284-1-memxor@gmail.com
> 
> Kumar Kartikeya Dwivedi (2):
>   bpf: Allow bpf_res_spin_lock() in all contexts
>   selftests/bpf: Test res spin locks in tracing programs
> 
> [...]

Here is the summary with links:
  - [bpf-next,v1,1/2] bpf: Allow bpf_res_spin_lock() in all contexts
    https://git.kernel.org/bpf/bpf-next/c/59b9731addc7
  - [bpf-next,v1,2/2] selftests/bpf: Test res spin locks in tracing programs
    (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-07-27 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 20:16 [PATCH bpf-next v1 0/2] Open up res_spin_lock() in all contexts Kumar Kartikeya Dwivedi
2026-07-24 20:16 ` [PATCH bpf-next v1 1/2] bpf: Allow bpf_res_spin_lock() " Kumar Kartikeya Dwivedi
2026-07-24 20:16 ` [PATCH bpf-next v1 2/2] selftests/bpf: Test res spin locks in tracing programs Kumar Kartikeya Dwivedi
2026-07-27 22: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=178519260713.1445878.13477862582196438048.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