From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] sched_ext: Source tree reorganization for v7.2
Date: Mon, 22 Jun 2026 11:32:20 -1000 [thread overview]
Message-ID: <e10b2679e4d0882e6d690c55c3efaa74@kernel.org> (raw)
Hello, Linus.
This is a follow-up to the v7.2 sched_ext pull, pure source tree
reorganization with no functional change. I'm sending it during the merge
window rather than a later cycle to reduce friction in routing fixes.
The following changes since commit ef0c9f75a19532d7675384708fc8621e10850104:
lib: Add stale 'raid6' directory to .gitignore file (2026-06-21 14:09:49 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git tags/sched_ext-for-7.2-1
for you to fetch changes up to 4437ad129cf5b37c00a5bc9fa5989d1da4d64d07:
sched_ext: Move shared helpers from ext.c into internal.h and cid.h (2026-06-22 10:41:34 -1000)
----------------------------------------------------------------
sched_ext: Source tree reorganization for v7.2
Follow-up to the v7.2 sched_ext pull. Pure source reorganization with no
functional change: the kernel/sched/ext* files move into a new
kernel/sched/ext/ subdirectory, and the headers and sources are made
self-contained so editor tooling can parse each file on its own.
----------------------------------------------------------------
Tejun Heo (3):
sched_ext: Move sources under kernel/sched/ext/
sched_ext: Make kernel/sched/ext/ sources self-contained for clangd
sched_ext: Move shared helpers from ext.c into internal.h and cid.h
Documentation/scheduler/sched-ext.rst | 8 +-
MAINTAINERS | 2 +-
kernel/sched/build_policy.c | 18 +--
kernel/sched/{ext_arena.c => ext/arena.c} | 4 +
kernel/sched/{ext_arena.h => ext/arena.h} | 2 +
kernel/sched/{ext_cid.c => ext/cid.c} | 5 +-
kernel/sched/{ext_cid.h => ext/cid.h} | 25 +++-
kernel/sched/{ => ext}/ext.c | 158 +++---------------------
kernel/sched/{ => ext}/ext.h | 0
kernel/sched/{ext_idle.c => ext/idle.c} | 3 +
kernel/sched/{ext_idle.h => ext/idle.h} | 4 +
kernel/sched/{ext_internal.h => ext/internal.h} | 129 +++++++++++++++++++
kernel/sched/{ext_types.h => ext/types.h} | 6 +
kernel/sched/sched.h | 2 +-
tools/sched_ext/include/scx/cid.bpf.h | 6 +-
15 files changed, 209 insertions(+), 163 deletions(-)
rename kernel/sched/{ext_arena.c => ext/arena.c} (98%)
rename kernel/sched/{ext_arena.h => ext/arena.h} (95%)
rename kernel/sched/{ext_cid.c => ext/cid.c} (99%)
rename kernel/sched/{ext_cid.h => ext/cid.h} (92%)
rename kernel/sched/{ => ext}/ext.c (98%)
rename kernel/sched/{ => ext}/ext.h (100%)
rename kernel/sched/{ext_idle.c => ext/idle.c} (99%)
rename kernel/sched/{ext_idle.h => ext/idle.h} (93%)
rename kernel/sched/{ext_internal.h => ext/internal.h} (93%)
rename kernel/sched/{ext_types.h => ext/types.h} (97%)
--
tejun
reply other threads:[~2026-06-22 21:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e10b2679e4d0882e6d690c55c3efaa74@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=emil@etsalapatis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=torvalds@linux-foundation.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