From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>
To: Andrea Righi <arighi@nvidia.com>
To: Changwoo Min <changwoo@igalia.com>
Cc: sched-ext@lists.linux.dev
Cc: Emil Tsalapatis <emil@etsalapatis.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET v2 sched_ext/for-7.3] sched_ext: Follow-up fixes and missing cap enforcement
Date: Fri, 24 Jul 2026 12:19:16 -1000 [thread overview]
Message-ID: <cd382b8b4f83b647bbe1f1840d9880c9@kernel.org> (raw)
In-Reply-To: <20260724191651.1040227-1-tj@kernel.org>
On Fri, Jul 24, 2026 at 09:16:46AM -1000, Tejun Heo wrote:
> 0001-tools-sched_ext-Don-t-restart-over-a-pending-exit-re.patch
> 0002-sched_ext-Gate-local-DSQ-reenq-on-baseline-cid-acces.patch
> 0003-sched_ext-Count-kicks-denied-for-lacking-baseline-ci.patch
> 0004-sched_ext-Factor-out-scx_cpuperf_set.patch
> 0005-sched_ext-Gate-scx_bpf_cidperf_set-behind-a-new-SCX_.patch
Applied 1-5 to sched_ext/for-7.3 with Andrea's Reviewed-by added.
Thanks.
--
tejun
prev parent reply other threads:[~2026-07-24 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 19:16 [PATCHSET v2 sched_ext/for-7.3] sched_ext: Follow-up fixes and missing cap enforcement Tejun Heo
2026-07-24 19:16 ` [PATCH 1/5] tools/sched_ext: Don't restart over a pending exit request Tejun Heo
2026-07-24 19:16 ` [PATCH 2/5] sched_ext: Gate local DSQ reenq on baseline cid access Tejun Heo
2026-07-24 19:16 ` [PATCH 3/5] sched_ext: Count kicks denied for lacking " Tejun Heo
2026-07-24 19:16 ` [PATCH 4/5] sched_ext: Factor out scx_cpuperf_set() Tejun Heo
2026-07-24 19:16 ` [PATCH 5/5] sched_ext: Gate scx_bpf_cidperf_set() behind a new SCX_CAP_PERF Tejun Heo
2026-07-24 19:57 ` [PATCHSET v2 sched_ext/for-7.3] sched_ext: Follow-up fixes and missing cap enforcement Andrea Righi
2026-07-24 22:19 ` 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=cd382b8b4f83b647bbe1f1840d9880c9@kernel.org \
--to=tj@kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.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