Received-SPF: pass (google.com: domain of linux-kernel+bounces-103540-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
From: Valentin Schneider <vschneid@redhat.com>
To: Maxim Moskalets <maximmosk4@gmail.com>, Ingo Molnar <mingo@redhat.com>,
 Peter Zijlstra <peterz@infradead.org>, Juri Lelli <juri.lelli@redhat.com>,
 Vincent Guittot <vincent.guittot@linaro.org>, Dietmar Eggemann
 <dietmar.eggemann@arm.com>, Steven Rostedt <rostedt@goodmis.org>, Ben
 Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>, Daniel Bristot
 de Oliveira <bristot@redhat.com>, linux-kernel@vger.kernel.org
Cc: Maxim Moskalets <Maxim.Moskalets@kaspersky.com>
Subject: Re: [PATCH] kernel/sched: use seq_putc instead of seq_puts
In-Reply-To: <20240303110500.15239-1-Maxim.Moskalets@kaspersky.com>
References: <20240303110500.15239-1-Maxim.Moskalets@kaspersky.com>
Date: Thu, 14 Mar 2024 17:00:22 +0100
Message-ID: <xhsmho7bgdcrt.mognet@vschneid-thinkpadt14sgen2i.remote.csb>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

On 03/03/24 14:05, Maxim Moskalets wrote:
> Using seq_putc for newline characters is faster and more appropriate
> than seq_puts, since only one character is passed and there is no need
> to use a more powerful and less fast function
>

Why not, but then why not do this treewide? A quick grep shows ~340 such
sites. That makes for a fairly easy coccinelle patch.