Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Markus Elfring <Markus.Elfring@web.de>,
	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 13:47:31 +0300	[thread overview]
Message-ID: <ai_YQwmgIFgWj0tj@stanley.mountain> (raw)
In-Reply-To: <ai_UUB7ouRSE1KEw@alpha.franken.de>

On Mon, Jun 15, 2026 at 12:30:40PM +0200, Thomas Bogendoerfer wrote:
> 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>

Generally, in most kernel subsystems the rule is that multi-line indents
get curly braces for readability even when they aren't required because
of the syntax.

regards,
dan carpenter


  reply	other threads:[~2026-06-15 10:47 UTC|newest]

Thread overview: 13+ 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
2026-06-15 10:47     ` Dan Carpenter [this message]
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

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_YQwmgIFgWj0tj@stanley.mountain \
    --to=error27@gmail.com \
    --cc=Markus.Elfring@web.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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