From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH]drivers:base:power:trace.c Add "UTC" Coordinated Universal Time to the printk.
Date: Sun, 12 Jun 2011 08:52:43 -0700 [thread overview]
Message-ID: <4DF4E0CB.4090900@gmail.com> (raw)
In-Reply-To: <201106121412.09903.rjw@sisk.pl>
On 06/12/2011 05:12 AM, Rafael J. Wysocki wrote:
> Hi,
>
> On Thursday, June 09, 2011, Justin P. Mattock wrote:
>> From: "Justin P. Mattock"<justinmattock@gmail.com>
>>
>> sounds stupid, but taking a glance at the time, and seeing the wrong time, or what seemed
>> wrong in dmesg, caused me to go into total check the time clock panic mode.. So the patch below adds:
>> "UTC" Coordinated Universal Time abreviation to the printk so people like me dont flip out over the time!
>>
>> before:
>> [ 0.114915] Time: 1:47:03 Date: 06/09/11
>>
>> after:
>> [ 0.114728] Time: 5:46:02 UTC Date: 06/09/11
>>
>> Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>
> I suspect the goal is to mark messages printed by the PM trace code so that
> they can be easily distinguished from messages from other sources to avoid
> confusion. Why do you think it's a good idea to use the "UTC" string for
> this purpose? The time printed in those messages need not be UTC.
>
> It would be better to simply print "RTC time: ..., date: ..." IMO.
>
> Thanks,
> Rafael
>
well.. if thats better, then thats better.. over here(people that dont
know what RTC time is) would not get so confused with a simple UTC or
PDT or whatever the time zone is but if RTC is bettr, then its better.
>
>> ---
>> drivers/base/power/trace.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/base/power/trace.c b/drivers/base/power/trace.c
>> index c80e138..009f459 100644
>> --- a/drivers/base/power/trace.c
>> +++ b/drivers/base/power/trace.c
>> @@ -112,7 +112,7 @@ static unsigned int read_magic_time(void)
>> unsigned int val;
>>
>> get_rtc_time(&time);
>> - pr_info("Time: %2d:%02d:%02d Date: %02d/%02d/%02d\n",
>> + pr_info("Time: %2d:%02d:%02d UTC Date: %02d/%02d/%02d\n",
>> time.tm_hour, time.tm_min, time.tm_sec,
>> time.tm_mon + 1, time.tm_mday, time.tm_year % 100);
>> val = time.tm_year; /* 100 years */
>>
>
>
next prev parent reply other threads:[~2011-06-12 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 6:01 [PATCH]drivers:base:power:trace.c Add "UTC" Coordinated Universal Time to the printk Justin P. Mattock
2011-06-12 12:12 ` Rafael J. Wysocki
2011-06-12 15:52 ` Justin P. Mattock [this message]
2011-06-12 18:35 ` Rafael J. Wysocki
2011-06-12 19:34 ` Justin P. Mattock
2011-06-12 20:27 ` Rafael J. Wysocki
2011-06-12 22:29 ` Justin P. Mattock
2011-06-13 21:47 ` Rafael J. Wysocki
2011-06-13 22:19 ` Justin P. Mattock
2011-06-14 20:02 ` Rafael J. Wysocki
2011-06-14 20:03 ` Justin P. Mattock
2011-06-19 6:28 ` Justin P. Mattock
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=4DF4E0CB.4090900@gmail.com \
--to=justinmattock@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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