* [MIPS] Separate CPU entries in /proc/cpuinfo with a blank line
@ 2006-03-20 2:51 Martin Michlmayr
2006-03-20 13:28 ` Ralf Baechle
0 siblings, 1 reply; 2+ messages in thread
From: Martin Michlmayr @ 2006-03-20 2:51 UTC (permalink / raw)
To: Ralf Baechle; +Cc: linux-mips
Put in a blank line between CPU entries in /proc/cpuinfo, just like
most other architectures (i386, ia64, x86_64) do.
Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
--- a/arch/mips/kernel/proc.c
+++ b/arch/mips/kernel/proc.c
@@ -135,6 +135,7 @@ static int show_cpuinfo(struct seq_file
cpu_has_vce ? "%u" : "not available");
seq_printf(m, fmt, 'D', vced_count);
seq_printf(m, fmt, 'I', vcei_count);
+ seq_printf(m, "\n");
return 0;
}
--
Martin Michlmayr
http://www.cyrius.com/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [MIPS] Separate CPU entries in /proc/cpuinfo with a blank line
2006-03-20 2:51 [MIPS] Separate CPU entries in /proc/cpuinfo with a blank line Martin Michlmayr
@ 2006-03-20 13:28 ` Ralf Baechle
0 siblings, 0 replies; 2+ messages in thread
From: Ralf Baechle @ 2006-03-20 13:28 UTC (permalink / raw)
To: Martin Michlmayr; +Cc: linux-mips
On Mon, Mar 20, 2006 at 02:51:20AM +0000, Martin Michlmayr wrote:
> Put in a blank line between CPU entries in /proc/cpuinfo, just like
> most other architectures (i386, ia64, x86_64) do.
Thanks, applied.
In the past I frequently used to reply to the mailing lists when applying
a patch. Since I resurrected the commits mailing lists I do no longer do
this. Just so people know.
Ralf
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-03-20 13:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-20 2:51 [MIPS] Separate CPU entries in /proc/cpuinfo with a blank line Martin Michlmayr
2006-03-20 13:28 ` Ralf Baechle
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox