From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
sched-ext@lists.linux.dev
Subject: Re: [PATCH sched_ext/for-7.2] sched_ext: Move sources under kernel/sched/ext/
Date: Mon, 22 Jun 2026 10:46:57 +0200 [thread overview]
Message-ID: <20260622084657.GZ49951@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260621163026.434856-1-tj@kernel.org>
On Sun, Jun 21, 2026 at 06:30:26AM -1000, Tejun Heo wrote:
> The sched_ext sources had grown to ten ext* files directly under
> kernel/sched/. Move them into a new kernel/sched/ext/ subdirectory and drop
> the now-redundant ext_ prefix. ext.c/h keep their names.
>
> kernel/sched/ext.{c,h} -> kernel/sched/ext/ext.{c,h}
> kernel/sched/ext_internal.h -> kernel/sched/ext/internal.h
> kernel/sched/ext_types.h -> kernel/sched/ext/types.h
> kernel/sched/ext_idle.{c,h} -> kernel/sched/ext/idle.{c,h}
> kernel/sched/ext_cid.{c,h} -> kernel/sched/ext/cid.{c,h}
> kernel/sched/ext_arena.{c,h} -> kernel/sched/ext/arena.{c,h}
>
> The include paths in build_policy.c and sched.h, the MAINTAINERS glob, and a
> few documentation and comment references are updated to match. No code or
> symbol changes.
>
> Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Tejun Heo <tj@kernel.org>
OK I suppose.
Can I take this opportunity to remind you that most of the ext files are
not clangd 'clean' yet. That is, they don't cleanly compile as stand
alone entities, which causes LSP/clangd enabled editors to throw a ton
of errors.
next prev parent reply other threads:[~2026-06-22 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 16:30 [PATCH sched_ext/for-7.2] sched_ext: Move sources under kernel/sched/ext/ Tejun Heo
2026-06-21 16:39 ` sashiko-bot
2026-06-21 18:34 ` [PATCH v2 " Tejun Heo
2026-06-21 19:09 ` Andrea Righi
2026-06-22 17:24 ` Tejun Heo
2026-06-22 8:46 ` Peter Zijlstra [this message]
2026-06-22 17:24 ` [PATCH " Tejun Heo
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=20260622084657.GZ49951@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=emil@etsalapatis.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--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