From: Maxim Moskalets <maximmosk4@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: maximmosk4@gmail.com, Maxim Moskalets <Maxim.Moskalets@kaspersky.com>
Subject: [PATCH 0/8] kernel: replace seq_puts by seq_putc
Date: Tue, 26 Mar 2024 21:45:14 +0300 [thread overview]
Message-ID: <20240326184514.8478-1-Maxim.Moskalets@kaspersky.com> (raw)
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.
Maxim Moskalets (8):
bpf: replace seq_puts by seq_putc
cgroup: replace seq_puts by seq_putc
trace: replace seq_puts by seq_putc
module: replace seq_puts by seq_putc
sched: replace seq_puts by seq_putc
locking: replace seq_puts by seq_putc
time: replace seq_puts by seq_putc
kernel: replace seq_puts by seq_putc
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(-)
base-commit: 928a87efa42302a23bb9554be081a28058495f22
--
2.39.2
next reply other threads:[~2024-03-26 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 18:45 Maxim Moskalets [this message]
2024-03-26 18:45 ` [PATCH 1/8] bpf: " Maxim Moskalets
2024-03-26 18:45 ` [PATCH 2/8] cgroup: " Maxim Moskalets
2024-03-26 18:46 ` [PATCH 3/8] trace: " Maxim Moskalets
2024-03-26 18:46 ` [PATCH 4/8] module: " Maxim Moskalets
2024-03-26 18:47 ` [PATCH 5/8] sched: " Maxim Moskalets
2024-03-26 18:47 ` [PATCH 6/8] locking: " Maxim Moskalets
2024-03-26 18:47 ` [PATCH 7/8] time: " Maxim Moskalets
2024-03-26 18:47 ` [PATCH 8/8] kernel: " Maxim Moskalets
2024-04-02 0:57 ` [PATCH 0/8] " Al Viro
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=20240326184514.8478-1-Maxim.Moskalets@kaspersky.com \
--to=maximmosk4@gmail.com \
--cc=Maxim.Moskalets@kaspersky.com \
--cc=linux-kernel@vger.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®