From: Steven Rostedt <rostedt@goodmis.org>
To: Maxim Moskalets <maximmosk4@gmail.com>
Cc: bristot@redhat.com, bsegall@google.com, dietmar.eggemann@arm.com,
juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
vincent.guittot@linaro.org, vschneid@redhat.com,
Maxim.Moskalets@kaspersky.com
Subject: Re: [PATCH RESEND] kernel: replace seq_puts by seq_putc
Date: Tue, 26 Mar 2024 12:13:03 -0400 [thread overview]
Message-ID: <20240326121303.7633eca8@gandalf.local.home> (raw)
In-Reply-To: <20240325192829.6710-1-Maxim.Moskalets@kaspersky.com>
On Mon, 25 Mar 2024 22:28:29 +0300
Maxim Moskalets <maximmosk4@gmail.com> wrote:
> Using seq_putc for single 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.
>
> Signed-off-by: Maxim Moskalets <Maxim.Moskalets@kaspersky.com>
> ---
> kernel/bpf/arraymap.c | 6 +++---
> kernel/bpf/bpf_struct_ops.c | 2 +-
> kernel/bpf/hashtab.c | 4 ++--
> kernel/bpf/local_storage.c | 4 ++--
> kernel/cgroup/cgroup.c | 2 +-
> kernel/cgroup/debug.c | 6 +++---
> kernel/latencytop.c | 2 +-
> kernel/locking/lockdep_proc.c | 24 ++++++++++++------------
> kernel/module/procfs.c | 4 ++--
> kernel/module/tracking.c | 2 +-
> kernel/sched/cpuacct.c | 4 ++--
> kernel/sched/debug.c | 14 +++++++-------
> kernel/time/test_udelay.c | 2 +-
> kernel/trace/trace_events_hist.c | 26 +++++++++++++-------------
> kernel/trace/trace_events_user.c | 8 ++++----
> kernel/trace/trace_hwlat.c | 4 ++--
> 16 files changed, 57 insertions(+), 57 deletions(-)
>
It's probably better to break this up per sub-system and send them out as
separate patches. At least that way the maintainers of the subsystems can
take the patch. Otherwise, nobody is going to take ownership of this.
-- Steve
> diff --git a/kernel/bpf/arraymap.c b/kernel/bpf/arraymap.c
prev parent reply other threads:[~2024-03-26 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 19:28 Maxim Moskalets
2024-03-26 16:13 ` 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=20240326121303.7633eca8@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Maxim.Moskalets@kaspersky.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maximmosk4@gmail.com \
--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®