From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Christian Loehle <christian.loehle@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Verify RCU protection in scx_bpf_cpu_curr()
Date: Tue, 23 Sep 2025 05:11:43 -1000 [thread overview]
Message-ID: <986d447360eba95adf07c893b4a3a43e@kernel.org> (raw)
In-Reply-To: <20250923091634.118240-1-arighi@nvidia.com>
> Andrea Righi (1):
> sched_ext: Verify RCU protection in scx_bpf_cpu_curr()
Applied to sched_ext/for-6.18.
Thanks.
--
tejun
prev parent reply other threads:[~2025-09-23 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 9:16 [PATCH] sched_ext: Verify RCU protection in scx_bpf_cpu_curr() Andrea Righi
2025-09-23 10:38 ` Kumar Kartikeya Dwivedi
2025-09-23 15:11 ` Tejun Heo [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=986d447360eba95adf07c893b4a3a43e@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=christian.loehle@arm.com \
--cc=linux-kernel@vger.kernel.org \
--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