mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: kernel-janitors@vger.kernel.org, Guan Xuetao <gxt@mprc.pku.edu.cn>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] unicore32/kernel/setup: Use seq_puts() in c_show()
Date: Sun, 7 May 2017 20:22:30 +0200	[thread overview]
Message-ID: <4299c720-a33e-238d-1b6e-abcfc45a07f7@users.sourceforge.net> (raw)

From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sun, 7 May 2017 20:15:41 +0200

Strings which did not contain data format specifications should be put
into a sequence. Thus use the corresponding function "seq_puts" more.

This issue was detected by using the Coccinelle software.

Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
 arch/unicore32/kernel/setup.c | 19 ++++++++-----------
 1 file changed, 8 insertions(+), 11 deletions(-)

diff --git a/arch/unicore32/kernel/setup.c b/arch/unicore32/kernel/setup.c
index c2bffa5614a4..345464ce35f5 100644
--- a/arch/unicore32/kernel/setup.c
+++ b/arch/unicore32/kernel/setup.c
@@ -316,18 +316,15 @@ static int c_show(struct seq_file *m, void *v)
 	seq_puts(m, "Features\t: CMOV UC-F64");
 
 	seq_printf(m, "\nCPU implementer\t: 0x%02x\n", uc32_cpuid >> 24);
-	seq_printf(m, "CPU architecture: 2\n");
+	seq_puts(m, "CPU architecture: 2\n");
 	seq_printf(m, "CPU revision\t: %d\n", (uc32_cpuid >> 16) & 15);
-
-	seq_printf(m, "Cache type\t: write-back\n"
-			"Cache clean\t: cp0 c5 ops\n"
-			"Cache lockdown\t: not support\n"
-			"Cache format\t: Harvard\n");
-
-	seq_puts(m, "\n");
-
-	seq_printf(m, "Hardware\t: PKUnity v3\n");
-
+	seq_puts(m,
+		 "Cache type\t: write-back\n"
+		 "Cache clean\t: cp0 c5 ops\n"
+		 "Cache lockdown\t: not support\n"
+		 "Cache format\t: Harvard\n"
+		 "\n"
+		 "Hardware\t: PKUnity v3\n");
 	return 0;
 }
 
-- 
2.12.2

                 reply	other threads:[~2017-05-07 22:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4299c720-a33e-238d-1b6e-abcfc45a07f7@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®