From: Markus Elfring <Markus.Elfring@web.de>
To: loongarch@lists.linux.dev, George Guo <dongtai.guo@linux.dev>,
Hengqi Chen <hengqi.chen@gmail.com>,
Huacai Chen <chenhuacai@kernel.org>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Wang Xuerui <kernel@xen0n.name>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 3/3] LoongArch: Combine two seq_puts() calls in show_cpuinfo()
Date: Thu, 4 Jun 2026 16:53:12 +0200 [thread overview]
Message-ID: <512f7a62-6f5d-46c5-b98a-f299616c8762@web.de> (raw)
In-Reply-To: <c36cab4c-0a91-4802-8693-a6ae3cee65b1@web.de>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 4 Jun 2026 16:33:07 +0200
Put data into a sequence by a single seq_puts() call instead of two.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
arch/loongarch/kernel/proc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/loongarch/kernel/proc.c b/arch/loongarch/kernel/proc.c
index bc1cd400025c..36df3c7f6990 100644
--- a/arch/loongarch/kernel/proc.c
+++ b/arch/loongarch/kernel/proc.c
@@ -57,9 +57,8 @@ static int show_cpuinfo(struct seq_file *m, void *v)
seq_puts(m, " loongarch32s");
if (isa & LOONGARCH_CPU_ISA_LA64)
seq_puts(m, " loongarch64");
- seq_puts(m, "\n");
- seq_puts(m, "Features\t\t:");
+ seq_puts(m, "\nFeatures\t\t:");
if (cpu_has_cpucfg)
seq_puts(m, " cpucfg");
if (cpu_has_lam)
--
2.54.0
next prev parent reply other threads:[~2026-06-04 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 14:48 [PATCH 0/3] LoongArch: More efficient data output " Markus Elfring
2026-06-04 14:50 ` [PATCH 1/3] LoongArch: Simplify " Markus Elfring
2026-06-04 14:51 ` [PATCH 2/3] LoongArch: Delete unnecessary braces " Markus Elfring
2026-06-04 14:53 ` Markus Elfring [this message]
2026-06-05 2:59 ` [PATCH 0/3] LoongArch: More efficient data output " Huacai Chen
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=512f7a62-6f5d-46c5-b98a-f299616c8762@web.de \
--to=markus.elfring@web.de \
--cc=chenhuacai@kernel.org \
--cc=dongtai.guo@linux.dev \
--cc=hengqi.chen@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@loongson.cn \
/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®