From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-mips@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 4/4] MIPS: kernel: proc: Delete unnecessary braces in show_cpuinfo()
Date: Mon, 15 Jun 2026 12:30:40 +0200 [thread overview]
Message-ID: <ai_UUB7ouRSE1KEw@alpha.franken.de> (raw)
In-Reply-To: <7c7d97b0-37bb-4e7b-9b2e-49a7c10eb6c5@web.de>
On Thu, Jun 04, 2026 at 07:56:12PM +0200, Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Thu, 4 Jun 2026 19:15:15 +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/mips/kernel/proc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/mips/kernel/proc.c b/arch/mips/kernel/proc.c
> index 42430c7f0acf..2c50b0b53be1 100644
> --- a/arch/mips/kernel/proc.c
> +++ b/arch/mips/kernel/proc.c
> @@ -151,10 +151,9 @@ static int show_cpuinfo(struct seq_file *m, void *v)
> seq_puts(m, " loongson-ext2");
> seq_putc(m, '\n');
>
> - if (cpu_has_mmips) {
> + if (cpu_has_mmips)
> seq_printf(m, "micromips kernel\t: %s\n",
> str_yes_no(read_c0_config3() & MIPS_CONF3_ISA_OE));
> - }
>
> seq_puts(m, "Options implemented\t:");
> if (cpu_has_tlb)
> --
> 2.54.0
applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2026-06-15 10:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 17:44 [PATCH 0/4] MIPS: kernel: proc: More efficient data output in show_cpuinfo() Markus Elfring
2026-06-04 17:50 ` [PATCH 1/4] MIPS: kernel: proc: Simplify " Markus Elfring
2026-06-04 17:51 ` [PATCH 2/4] MIPS: kernel: proc: Combine two seq_puts() calls " Markus Elfring
2026-06-04 17:54 ` [PATCH 3/4] MIPS: kernel: proc: Use seq_putc() " Markus Elfring
2026-06-15 10:30 ` Thomas Bogendoerfer
2026-06-04 17:56 ` [PATCH 4/4] MIPS: kernel: proc: Delete unnecessary braces " Markus Elfring
2026-06-15 10:30 ` Thomas Bogendoerfer [this message]
2026-06-15 10:47 ` Dan Carpenter
2026-06-15 10:53 ` [4/4] " Markus Elfring
2026-06-15 11:13 ` Markus Elfring
2026-06-05 2:58 ` [PATCH 0/4] MIPS: kernel: proc: More efficient data output " Huacai Chen
2026-06-16 10:34 ` [0/4] " Markus Elfring
2026-06-16 11:00 ` Thomas Bogendoerfer
2026-06-22 15:57 ` [PATCH] MIPS: kernel: proc: Use two seq_putc() calls " Markus Elfring
2026-07-17 11:02 ` Thomas Bogendoerfer
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=ai_UUB7ouRSE1KEw@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Markus.Elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.