From: Markus Elfring <Markus.Elfring@web.de>
To: Hao Jia <jiahao1@lixiang.com>,
kernel-janitors@vger.kernel.org, Ben Segall <bsegall@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>, Mel Gorman <mgorman@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Valentin Schneider <vschneid@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: Hao Jia <jiahao.kernel@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [v2] sched/core: Prioritize migrating eligible tasks in sched_balance_rq()
Date: Tue, 24 Dec 2024 09:55:39 +0100 [thread overview]
Message-ID: <015b9bbf-8268-4da6-b6dd-bdbcbef7ec34@web.de> (raw)
In-Reply-To: <2cfea522-8015-d86b-f78d-a6a2c56ba8b8@gmail.com>
>> You may occasionally put more than 63 characters into text lines
>> of such a change description.
>
> I checked the patch using ./scripts/checkpatch.pl before sending it, and found no warnings or errors. The commit log should preferably have less than 75 characters per line.
Can any texts look nicer if word wrapping would be accordingly adjusted a bit more?
Regards,
Markus
next prev parent reply other threads:[~2024-12-24 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 9:14 [PATCH v2] " Hao Jia
2024-12-23 20:50 ` Markus Elfring
2024-12-24 1:53 ` Hao Jia
2024-12-24 8:55 ` Markus Elfring [this message]
2025-01-13 9:21 ` Hao Jia
2025-01-13 16:40 ` Vincent Guittot
2025-01-14 3:18 ` Hao Jia
2025-01-14 8:07 ` Vincent Guittot
2025-01-15 8:55 ` Hao Jia
2025-01-15 9:28 ` Vincent Guittot
2025-01-15 11:55 ` Hao Jia
2025-01-16 11:26 ` Vincent Guittot
2025-01-20 5:48 ` Hao Jia
2025-02-17 6:13 ` Hao Jia
2025-01-15 9:17 ` [tip: sched/core] " tip-bot2 for Hao Jia
2025-01-15 13:18 ` [PATCH v2] " Luis Machado
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=015b9bbf-8268-4da6-b6dd-bdbcbef7ec34@web.de \
--to=markus.elfring@web.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jiahao.kernel@gmail.com \
--cc=jiahao1@lixiang.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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®