From: Zhan Xusheng <zhanxusheng1024@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-sched@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: [PATCH 0/2] sched/fair: cleanups and readability fixes
Date: Fri, 19 Dec 2025 16:50:03 +0800 [thread overview]
Message-ID: <20251219085005.50906-1-zhanxusheng@xiaomi.com> (raw)
This series contains two small cleanups in the CFS scheduler:
1. Fix misuse of the comma operator in NUMA fault accounting by
replacing it with explicit statements, improving readability.
2. Replace bare 'unsigned' casts with explicit 'unsigned int' casts
to comply with kernel coding style.
No functional changes intended.
Thanks,
Zhan Xusheng
--
2.43.0
next reply other threads:[~2025-12-19 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 8:50 Zhan Xusheng [this message]
2025-12-19 8:50 ` [PATCH 1/2] sched/fair: fix comma operator misuse in NUMA fault accounting Zhan Xusheng
2025-12-19 10:54 ` Peter Zijlstra
2025-12-19 8:50 ` [PATCH 2/2] sched/fair: replace bare 'unsigned' with 'unsigned int' Zhan Xusheng
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=20251219085005.50906-1-zhanxusheng@xiaomi.com \
--to=zhanxusheng1024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sched@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=zhanxusheng@xiaomi.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