From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Justin P. Mattock" <justinmattock@gmail.com>
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: Mon, 13 Jun 2011 23:47:07 +0200 [thread overview]
Message-ID: <201106132347.08007.rjw@sisk.pl> (raw)
In-Reply-To: <4DF53DCC.1060604@gmail.com>
On Monday, June 13, 2011, Justin P. Mattock wrote:
> On 06/12/2011 01:27 PM, Rafael J. Wysocki wrote:
> > On Sunday, June 12, 2011, Justin P. Mattock wrote:
> >> On 06/12/2011 11:35 AM, Rafael J. Wysocki wrote:
> >>> On Sunday, June 12, 2011, Justin P. Mattock wrote:
> >>>> 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.
> >>>
> >>> My point is we don't know this time is always UTC, so we rather shouldn't
> >>> label it as UTC unconditionally, should we?
> >>>
> >>> Rafael
> >>>
> >>
> >> sounds good to me!!
> >
> > I'm not sure what you mean?
> >
>
> with what you are saying "RTC" if anything.. rather than "UTC"
So, it looks like you'd like the appended patch to be appiled?
Rafael
---
From: Rafael J. Wysocki <rjw@sisk.pl>
Subject: PM: Add "RTC" to PM trace time stamps to avoid confusion
Some users are apparently confused by dmesg output from
read_magic_time(), which looks like "real" time and date.
Add the "RTC" string to time stamps printed by read_magic_time() to
avoid that confusion.
Reported-by: Justin P. Mattock <justinmattock@gmail.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
---
drivers/base/power/trace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/drivers/base/power/trace.c
===================================================================
--- linux-2.6.orig/drivers/base/power/trace.c
+++ linux-2.6/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("RTC time: %2d:%02d:%02d, 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-13 21:46 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
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 [this message]
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=201106132347.08007.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=justinmattock@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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