[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <015b9bbf-8268-4da6-b6dd-bdbcbef7ec34@web.de>
Date: Tue, 24 Dec 2024 09:55:39 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Hao Jia <jiahao1@...iang.com>, kernel-janitors@...r.kernel.org,
Ben Segall <bsegall@...gle.com>, Dietmar Eggemann
<dietmar.eggemann@....com>, Ingo Molnar <mingo@...nel.org>,
Juri Lelli <juri.lelli@...hat.com>, Mel Gorman <mgorman@...e.de>,
Peter Zijlstra <peterz@...radead.org>, Steven Rostedt <rostedt@...dmis.org>,
Valentin Schneider <vschneid@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>
Cc: Hao Jia <jiahao.kernel@...il.com>, LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [v2] sched/core: Prioritize migrating eligible tasks in
sched_balance_rq()
>> 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
Powered by blists - more mailing lists