From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>
Cc: sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
Emil Tsalapatis <emil@etsalapatis.com>,
David Dai <david.dai@linux.dev>, Tao Cui <cui.tao@linux.dev>
Subject: Re: [PATCH sched_ext/for-7.4] sched_ext: Clear a sub-scheduler's caps before ops.sub_detach()
Date: Tue, 06 Oct 2026 12:14:38 -1000 [thread overview]
Message-ID: <5db00088481030c82f8ad1a6aa59e581@kernel.org> (raw)
In-Reply-To: <b46300eda6da03d56262fcdcbfc9b4fa@kernel.org>
On Tue, Oct 06, 2026 at 10:31:48AM -1000, Tejun Heo wrote:
> Applied to sched_ext/for-7.4.
Applying this was an accident and premature. I'm going to leave it as-is
but please holler if you see any issues.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-10-06 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 20:31 [PATCH sched_ext/for-7.4] sched_ext: Clear a sub-scheduler's caps before ops.sub_detach() Tejun Heo
2026-10-06 20:44 ` sashiko-bot
2026-10-06 22:14 ` Tejun Heo [this message]
2026-10-08 4:39 ` Tao Cui
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=5db00088481030c82f8ad1a6aa59e581@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=cui.tao@linux.dev \
--cc=david.dai@linux.dev \
--cc=emil@etsalapatis.com \
--cc=linux-kernel@vger.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 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.