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,
Huacai Chen <chenhuacai@kernel.org>
Subject: Re: [PATCH] MIPS: kernel: proc: Use two seq_putc() calls in show_cpuinfo()
Date: Fri, 17 Jul 2026 13:02:33 +0200 [thread overview]
Message-ID: <aloLyYPIV39N_tQb@alpha.franken.de> (raw)
In-Reply-To: <736e312c-1356-4d8f-8ae5-bcc695f555dc@web.de>
On Mon, Jun 22, 2026 at 05:57:34PM +0200, Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Mon, 22 Jun 2026 17:50:13 +0200
>
> Single line breaks should occasionally be put into a sequence.
> Thus use the corresponding function “seq_putc”.
>
> The source code was transformed by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
> arch/mips/kernel/proc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/kernel/proc.c b/arch/mips/kernel/proc.c
> index 5401c679813a..5f49fd4653a7 100644
> --- a/arch/mips/kernel/proc.c
> +++ b/arch/mips/kernel/proc.c
> @@ -109,7 +109,7 @@ static int show_cpuinfo(struct seq_file *m, void *v)
> seq_puts(m, " mips64r5");
> if (cpu_has_mips64r6)
> seq_puts(m, " mips64r6");
> - seq_puts(m, "\n");
> + seq_putc(m, '\n');
>
> seq_puts(m, "ASEs implemented\t:");
> if (cpu_has_mips16)
> @@ -273,7 +273,7 @@ static int show_cpuinfo(struct seq_file *m, void *v)
> seq_puts(m, " mm_sysad");
> if (cpu_has_mm_full)
> seq_puts(m, " mm_full");
> - seq_puts(m, "\n");
> + seq_putc(m, '\n');
>
> seq_printf(m, "shadow register sets\t: %d\n",
> cpu_data[n].srsets);
> --
> 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 ]
prev parent reply other threads:[~2026-07-17 11:05 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
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 [this message]
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=aloLyYPIV39N_tQb@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Markus.Elfring@web.de \
--cc=chenhuacai@kernel.org \
--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.