From: Markus Elfring <Markus.Elfring@web.de>
To: linux-mips@vger.kernel.org,
"Thomas Bogendörfer" <tsbogend@alpha.franken.de>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/4] MIPS: kernel: proc: More efficient data output in show_cpuinfo()
Date: Thu, 4 Jun 2026 19:44:29 +0200 [thread overview]
Message-ID: <e9e46083-c250-4e12-8620-f590e9501a25@web.de> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 4 Jun 2026 19:33:55 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Simplify data output
Combine two seq_puts() calls
Use seq_putc() calls
Delete unnecessary braces
arch/mips/kernel/proc.c | 16 ++++++----------
1 file changed, 6 insertions(+), 10 deletions(-)
--
2.54.0
next reply other threads:[~2026-06-04 17:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 17:44 Markus Elfring [this message]
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
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=e9e46083-c250-4e12-8620-f590e9501a25@web.de \
--to=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