From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Print cpuid along with the timestamp with CONFIG_PRINTK_TIME
Date: Fri, 19 Sep 2008 11:39:36 -0700 [thread overview]
Message-ID: <20080919183936.GA28992@localdomain> (raw)
In-Reply-To: <20080919171516.GB5540@joi>
On Fri, Sep 19, 2008 at 07:15:21PM +0200, Marcin Slusarz wrote:
>
>Do we really need this information on UP kernels?
I thought about it, and left it as the way it is to have a consistent format
between UP and SMP. With most of the modern cpus being multicore, or headed
that way, and since the entire timestamp prefix can be controlled by a boot
option, is it worth having different formats for UP and SMP? Most distros
ship SMP kernels anyways.
prev parent reply other threads:[~2008-09-19 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 19:37 [PATCH] printk: Print cpuid along with the timestamp with CONFIG_PRINTK_TIME Ravikiran G Thirumalai
2008-09-18 19:51 ` Andrew Morton
2008-09-19 0:35 ` Ravikiran G Thirumalai
2008-09-19 17:15 ` Marcin Slusarz
2008-09-19 18:39 ` Ravikiran G Thirumalai [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=20080919183936.GA28992@localdomain \
--to=kiran@scalex86.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
/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