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: Re: [0/4] MIPS: kernel: proc: More efficient data output in show_cpuinfo()
Date: Tue, 16 Jun 2026 12:34:18 +0200 [thread overview]
Message-ID: <39fa676a-e761-4a33-9660-f366c692d4f1@web.de> (raw)
In-Reply-To: <e9e46083-c250-4e12-8620-f590e9501a25@web.de>
> A few update suggestions were taken into account
> from static source code analysis.
Does the feedback indicate so far that you would like to omit
the patch “MIPS: kernel: proc: Simplify data output in show_cpuinfo()”?
https://lore.kernel.org/linux-mips/5dcb1ae4-dc98-4f12-8ccb-ff47b16a326c@web.de/
https://lkml.org/lkml/2026/6/4/1819
Will another source code adjustment become helpful?
Regards,
Markus
next prev parent reply other threads:[~2026-06-16 10:35 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
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 ` Markus Elfring [this message]
2026-06-16 11:00 ` [0/4] " 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=39fa676a-e761-4a33-9660-f366c692d4f1@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