All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, rcu@vger.kernel.org, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
	eddyz87@gmail.com, memxor@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, harry@kernel.org, paulmck@kernel.org
Subject: Re: [PATCH bpf-next v6 0/4] bpf: Add bpf_call_rcu() and bpf_call_rcu_tasks_trace()
Date: Tue, 22 Sep 2026 23:50:19 +0000	[thread overview]
Message-ID: <179012101963.134796.5104936283975615071.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922200208.3203834-1-puranjay@kernel.org>

Hello:

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

On Tue, 22 Sep 2026 13:00:49 -0700 you wrote:
> Changelog:
> v5: https://lore.kernel.org/all/20260921191407.1742386-1-puranjay@kernel.org/
> Changes in v6:
> - Size struct bpf_rcu_head at 48 bytes rather than 64, matching what the
>   inline state uses (Alexei)
> - Trim patch 1's changelog: drop the reasoning about possible future
>   layouts and about what the other async kfuncs return
> - Rebase on bpf-next/master
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,1/4] bpf: Add bpf_call_rcu() kfunc
    https://git.kernel.org/bpf/bpf-next/c/1832696b2207
  - [bpf-next,v6,2/4] selftests/bpf: Add tests for bpf_call_rcu()
    https://git.kernel.org/bpf/bpf-next/c/908a60853b8d
  - [bpf-next,v6,3/4] bpf: Add bpf_call_rcu_tasks_trace() kfunc
    https://git.kernel.org/bpf/bpf-next/c/db1b20ed6b09
  - [bpf-next,v6,4/4] selftests/bpf: Add a test for bpf_call_rcu_tasks_trace()
    https://git.kernel.org/bpf/bpf-next/c/b22f65a009ad

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-22 23:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 20:00 [PATCH bpf-next v6 0/4] bpf: Add bpf_call_rcu() and bpf_call_rcu_tasks_trace() Puranjay Mohan
2026-09-22 20:00 ` [PATCH bpf-next v6 1/4] bpf: Add bpf_call_rcu() kfunc Puranjay Mohan
2026-09-22 20:00 ` [PATCH bpf-next v6 2/4] selftests/bpf: Add tests for bpf_call_rcu() Puranjay Mohan
2026-09-22 20:00 ` [PATCH bpf-next v6 3/4] bpf: Add bpf_call_rcu_tasks_trace() kfunc Puranjay Mohan
2026-09-22 20:37   ` sashiko-bot
2026-09-22 20:00 ` [PATCH bpf-next v6 4/4] selftests/bpf: Add a test for bpf_call_rcu_tasks_trace() Puranjay Mohan
2026-09-22 23:41 ` [PATCH bpf-next v6 0/4] bpf: Add bpf_call_rcu() and bpf_call_rcu_tasks_trace() Andrii Nakryiko
2026-09-23 10:37   ` Puranjay Mohan
2026-09-23 11:29     ` Kumar Kartikeya Dwivedi
2026-09-23 16:45       ` Andrii Nakryiko
2026-09-23 16:53         ` Kumar Kartikeya Dwivedi
2026-09-23 16:59           ` Andrii Nakryiko
2026-09-23 17:57             ` Kumar Kartikeya Dwivedi
2026-09-23 18:21               ` Andrii Nakryiko
2026-09-23 18:30                 ` Puranjay Mohan
2026-09-23 19:25                   ` Andrii Nakryiko
2026-09-22 23: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=179012101963.134796.5104936283975615071.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=harry@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=puranjay@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.