public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Boqun Feng <boqun@kernel.org>
Cc: torvalds@linux-foundation.org, paulmck@kernel.org,
	frederic@kernel.org, neeraj.upadhyay@kernel.org,
	joelagnelf@nvidia.com, urezki@gmail.com,
	linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
	ast@kernel.org, memxor@gmail.com, bpf@vger.kernel.org,
	arighi@nvidia.com
Subject: Re: [GIT PULL] RCU fixes for v7.0 (part 2)
Date: Thu, 26 Mar 2026 19:12:49 +0000	[thread overview]
Message-ID: <177455236929.3138649.14628219359281836881.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <acRho9L4zA2MRuxc@tardis.local>

Hello:

This pull request was applied to netdev/net.git (main)
by Linus Torvalds <torvalds@linux-foundation.org>:

On Wed, 25 Mar 2026 15:28:51 -0700 you wrote:
> Hi Linus,
> 
> This is another set fixes for RCU in v7.0-rc, please pull these into
> v7.0. The issue is since we replace the Tasks Trace RCU in tracing
> (e.g. BPF) with SRCU, SRCU has to work in preemption disabled or
> scheduler lock held contexts, which was missing in v7.0 RCU pull
> request.
> 
> [...]

Here is the summary with links:
  - [GIT,PULL] RCU fixes for v7.0 (part 2)
    https://git.kernel.org/netdev/net/c/aba9da0905f1

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-03-26 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 22:28 [GIT PULL] RCU fixes for v7.0 (part 2) Boqun Feng
2026-03-26  1:52 ` pr-tracker-bot
2026-03-26 19:12 ` 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=177455236929.3138649.14628219359281836881.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=ast@kernel.org \
    --cc=boqun@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=frederic@kernel.org \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=memxor@gmail.com \
    --cc=neeraj.upadhyay@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=urezki@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