From: Steven Rostedt <rostedt@goodmis.org>
To: XueBing Chen <chenxb_99091@126.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: Fix code indentation at line 10371
Date: Fri, 17 Oct 2025 04:58:17 -0400 [thread overview]
Message-ID: <20251017045817.137483e1@batman.local.home> (raw)
In-Reply-To: <20251017064152.48490-1-chenxb_99091@126.com>
On Fri, 17 Oct 2025 14:41:52 +0800
XueBing Chen <chenxb_99091@126.com> wrote:
> Fix checkpatch.pl indentation warning by replacing spaces with tab.
checkpatch.ps is to be used on patches *AND NEVER EXISTING CODE*!
Please do not "fix" existing code with what checkpatch complains about,
unless it's a real bug. That's not its purpose. This just adds noise to
the git log.
NAK.
-- Steve
>
> Signed-off-by: XueBing Chen <chenxb_99091@126.com>
> ---
> kernel/sched/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 198d2dd45..24fd78d42 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -10368,7 +10368,7 @@ const u32 sched_prio_to_wmult[40] = {
>
> void call_trace_sched_update_nr_running(struct rq *rq, int count)
> {
> - trace_sched_update_nr_running_tp(rq, count);
> + trace_sched_update_nr_running_tp(rq, count);
> }
>
> #ifdef CONFIG_SCHED_MM_CID
prev parent reply other threads:[~2025-10-17 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 6:41 XueBing Chen
2025-10-17 8:58 ` Steven Rostedt [this message]
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=20251017045817.137483e1@batman.local.home \
--to=rostedt@goodmis.org \
--cc=bsegall@google.com \
--cc=chenxb_99091@126.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®