mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 2/3] LoongArch: Delete unnecessary braces in show_cpuinfo()
Date: Thu, 4 Jun 2026 16:51:57 +0200	[thread overview]
Message-ID: <b01a6836-87a7-479a-90a8-3542e8d1b9eb@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:16:43 +0200

Do not use curly brackets at one source code place
where a single statement should be sufficient.

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 cc1b7a96bb0f..bc1cd400025c 100644
--- a/arch/loongarch/kernel/proc.c
+++ b/arch/loongarch/kernel/proc.c
@@ -96,10 +96,9 @@ static int show_cpuinfo(struct seq_file *m, void *v)
 		seq_puts(m, " lbt_mips");
 
 	seq_printf(m, "\nHardware Watchpoint\t: %s", str_yes_no(cpu_has_watch));
-	if (cpu_has_watch) {
+	if (cpu_has_watch)
 		seq_printf(m, ", iwatch count: %d, dwatch count: %d",
 		      cpu_data[n].watch_ireg_count, cpu_data[n].watch_dreg_count);
-	}
 
 	seq_puts(m, "\n\n");
 
-- 
2.54.0


  parent reply	other threads:[~2026-06-04 14:52 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 ` Markus Elfring [this message]
2026-06-04 14:53 ` [PATCH 3/3] LoongArch: Combine two seq_puts() calls " Markus Elfring
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=b01a6836-87a7-479a-90a8-3542e8d1b9eb@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®