From: Cheng-Yang Chou <yphbchou0911@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: tj@kernel.org, void@manifault.com, arighi@nvidia.com,
changwoo@igalia.com, jserv@ccns.ncku.edu.tw,
yphbchou0911@gmail.com
Subject: [PATCH 0/4] sched_ext: Standardize preprocessor comment markers
Date: Wed, 11 Jun 2025 21:54:00 +0800 [thread overview]
Message-ID: <20250611135404.13851-1-yphbchou0911@gmail.com> (raw)
This series standardizes `#if/#else/#endif` comment markers in the
`sched/ext*.{c,h}` files for consistency and readability.
It follows the direction of Ingo Molnar's recent cleanup
("[PATCH 00/43] sched: Use the SMP scheduler on UP too"), which reduced
`CONFIG_SMP` complexity and removed many `#ifdef` blocks across the scheduler.
No functional change.
Thanks.
-chengyang
---
Cheng-Yang Chou (4):
sched_ext: Clean up and standardize #if/#else/#endif markers in
sched/ext.c
sched_ext: Clean up and standardize #if/#else/#endif markers in
sched/ext.h
sched_ext: Clean up and standardize #if/#else/#endif markers in
sched/ext_idle.c
sched_ext: Clean up and standardize #if/#else/#endif markers in
sched/ext_idle.h
kernel/sched/ext.c | 26 +-------------------------
kernel/sched/ext.h | 2 +-
kernel/sched/ext_idle.c | 25 +------------------------
kernel/sched/ext_idle.h | 10 ----------
4 files changed, 3 insertions(+), 60 deletions(-)
--
2.43.0
next reply other threads:[~2025-06-11 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 13:54 Cheng-Yang Chou [this message]
2025-06-11 13:54 ` [PATCH 1/4] sched_ext: Clean up and standardize #if/#else/#endif markers in sched/ext.c Cheng-Yang Chou
2025-06-11 13:54 ` [PATCH 2/4] sched_ext: Clean up and standardize #if/#else/#endif markers in sched/ext.h Cheng-Yang Chou
2025-06-11 13:54 ` [PATCH 3/4] sched_ext: Clean up and standardize #if/#else/#endif markers in sched/ext_idle.c Cheng-Yang Chou
2025-06-14 0:49 ` Tejun Heo
2025-06-11 13:54 ` [PATCH 4/4] sched_ext: Clean up and standardize #if/#else/#endif markers in sched/ext_idle.h Cheng-Yang Chou
2025-06-14 0:42 ` [PATCH 0/4] sched_ext: Standardize preprocessor comment markers Tejun Heo
2025-06-14 8:06 ` Cheng-Yang Chou
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=20250611135404.13851-1-yphbchou0911@gmail.com \
--to=yphbchou0911@gmail.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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