From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 2/3] powerpc: Make newline in cpuinfo unconditional
Date: Wed, 10 Jan 2018 17:10:13 +1100 [thread overview]
Message-ID: <20180110061014.29181-2-benh@kernel.crashing.org> (raw)
In-Reply-To: <20180110061014.29181-1-benh@kernel.crashing.org>
We used to not put the newline between the CPU part and the summary
part on UP kernels. This is a rather pointless ifdef so take it out.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/powerpc/kernel/setup-common.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/setup-common.c b/arch/powerpc/kernel/setup-common.c
index 8fd3a70047f1..c1df4ba0094c 100644
--- a/arch/powerpc/kernel/setup-common.c
+++ b/arch/powerpc/kernel/setup-common.c
@@ -346,10 +346,8 @@ static int show_cpuinfo(struct seq_file *m, void *v)
loops_per_jiffy / (500000/HZ),
(loops_per_jiffy / (5000/HZ)) % 100);
#endif
-
-#ifdef CONFIG_SMP
seq_printf(m, "\n");
-#endif
+
/* If this is the last cpu, print the summary */
if (cpumask_next(cpu_id, cpu_online_mask) >= nr_cpu_ids)
show_cpuinfo_summary(m);
--
2.14.3
next prev parent reply other threads:[~2018-01-10 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 6:10 [PATCH 1/3] powerpc: Don't preempt_disable() in show_cpuinfo() Benjamin Herrenschmidt
2018-01-10 6:10 ` Benjamin Herrenschmidt [this message]
2018-01-17 13:30 ` [2/3] powerpc: Make newline in cpuinfo unconditional Michael Ellerman
2018-01-10 6:10 ` [PATCH 3/3] powerpc: Cosmetic cleanup of cpuinfo_op Benjamin Herrenschmidt
2018-01-17 13:30 ` [3/3] " Michael Ellerman
2018-01-15 10:16 ` [1/3] powerpc: Don't preempt_disable() in show_cpuinfo() Michael Ellerman
2018-01-17 13:25 ` Michael Ellerman
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=20180110061014.29181-2-benh@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).