From: Jahan Zaib Ashraf Mir <jahanzaibashraf1318@gmail.com>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org
Cc: linux-kernel@vger.kernel.org,
Jahan Zaib Ashraf Mir <jahanzaibashraf1318@gmail.com>
Subject: [PATCH] sched/core: fix coding style issues
Date: Fri, 2 Oct 2026 19:06:26 +0530 [thread overview]
Message-ID: <20261002133626.20443-1-jahanzaibashraf1318@gmail.com> (raw)
Fix three checkpatch warnings in sched/core.c:
- Use 'unsigned int' instead of bare 'unsigned' for mode parameter
in default_wake_function()
- Add missing blank line after variable declaration in
__sched_setscheduler()
- Add missing blank line after variable declaration in
sched_dynamic_update()
Signed-off-by: Jahan Zaib Ashraf Mir <jahanzaibashraf1318@gmail.com>
---
kernel/sched/core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index e8c46f849f6e..9bd1bf3d7729 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -4723,6 +4723,7 @@ void force_schedstat_enabled(void)
static int __init setup_schedstats(char *str)
{
int ret = 0;
+
if (!str)
goto out;
@@ -7611,7 +7612,7 @@ asmlinkage __visible void __sched preempt_schedule_irq(void)
exception_exit(prev_state);
}
-int default_wake_function(wait_queue_entry_t *curr, unsigned mode, int wake_flags,
+int default_wake_function(wait_queue_entry_t *curr, unsigned int mode, int wake_flags,
void *key)
{
WARN_ON_ONCE(wake_flags & ~(WF_SYNC|WF_CURRENT_CPU));
@@ -8087,6 +8088,7 @@ static int __init setup_preempt_mode(char *str)
{
int mode = sched_dynamic_mode(str);
if (mode < 0) {
+
pr_warn("Dynamic Preempt: unsupported mode: %s\n", str);
return 0;
}
--
2.56.0
next reply other threads:[~2026-10-02 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 13:36 Jahan Zaib Ashraf Mir [this message]
2026-10-05 13:46 ` Phil Auld
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=20261002133626.20443-1-jahanzaibashraf1318@gmail.com \
--to=jahanzaibashraf1318@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
/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
all inboxes | Powered by JetHome®