From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Waiman Long <longman@redhat.com>,
kernel-janitors@vger.kernel.org,
Boqun Feng <boqun.feng@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH] locking/lockdep: Use seq_putc() in five functions
Date: Mon, 15 Jul 2024 07:18:57 +0200 [thread overview]
Message-ID: <7560b341-27b4-45b9-8b73-202ec7f27200@wanadoo.fr> (raw)
In-Reply-To: <975d2b0f-f84c-4c84-adf2-098fef59d90b@redhat.com>
Le 14/07/2024 à 23:31, Waiman Long a écrit :
> On 7/14/24 06:25, Markus Elfring wrote:
>> From: Markus Elfring <elfring@users.sourceforge.net>
>> Date: Sun, 14 Jul 2024 12:18:16 +0200
>>
>> Single characters should be put into a sequence.
>> Thus use the corresponding function “seq_putc”.
>>
>> This issue was transformed by using the Coccinelle software.
>>
>> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
>> ---
...
>> @@ -422,10 +422,10 @@ static void seq_line(struct seq_file *m, char c,
>> int offset, int length)
>> int i;
>>
>> for (i = 0; i < offset; i++)
>> - seq_puts(m, " ");
>> + seq_putc(m, ' ');
Hi,
Most of the time, this kind of modification is useless because it is
already done by the compiler, see [1].
>> for (i = 0; i < length; i++)
>> seq_printf(m, "%c", c);
But changing this seq_printf() into a seq_putc() would, IMHO, make sense
and save a few cycles, should it matter.
CJ
[1]:
https://elixir.bootlin.com/linux/v6.10-rc7/source/include/linux/seq_file.h#L123
>> - seq_puts(m, "\n");
>> + seq_putc(m, '\n');
>> }
>>
...
>> --
>> 2.45.2
>>
> Acked-by: Waiman Long <longman@redhat.com>
>
next prev parent reply other threads:[~2024-07-15 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 10:25 Markus Elfring
2024-07-14 21:31 ` Waiman Long
2024-07-15 5:18 ` Christophe JAILLET [this message]
2024-07-15 8:51 ` [PATCH] locking/lockdep: Simplify character output in seq_line() Markus Elfring
2024-08-05 17:46 ` Boqun Feng
2024-08-08 10:22 ` [tip: locking/core] " tip-bot2 for Markus Elfring
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=7560b341-27b4-45b9-8b73-202ec7f27200@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=Markus.Elfring@web.de \
--cc=boqun.feng@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.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®