From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Joe Perches <joe@perches.com>
Cc: Shuah Khan <shuah.kh@samsung.com>, "pavel@ucw.cz" <pavel@ucw.cz>,
"len.brown@intel.com" <len.brown@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shuahkhan@gmail.com" <shuahkhan@gmail.com>
Subject: Re: [PATCHv v3] power: Include additional information in pm_print_times
Date: Sun, 23 Jun 2013 23:59:03 +0200 [thread overview]
Message-ID: <7303551.DgZO2t6GUO@vostro.rjw.lan> (raw)
In-Reply-To: <1371987257.3137.44.camel@joe-AO722>
On Sunday, June 23, 2013 04:34:17 AM Joe Perches wrote:
> On Sun, 2013-06-23 at 13:36 +0200, Rafael J. Wysocki wrote:
> > Please keep the existing format as is literally and append any
> > new information to the end of the line.
>
> Hi Shuah.
>
> Perhaps the better long-term approach would be to add
> a new tracepoint too.
In fact, I would even prefer it if new tracepoints were added so that we
could deprecate the dmesg messages at one point in the future.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-06-23 21:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 19:36 [PATCHv v3] power: Include additional information in pm_print_times Shuah Khan
2013-06-17 19:41 ` Greg KH
2013-06-17 20:24 ` Alan Stern
2013-06-17 20:24 ` Alan Stern
2013-06-18 14:54 ` Shuah Khan
2013-06-22 0:24 ` Rafael J. Wysocki
2013-06-22 0:58 ` Shuah Khan
2013-06-23 11:36 ` Rafael J. Wysocki
2013-06-23 11:34 ` Joe Perches
2013-06-23 21:59 ` Rafael J. Wysocki [this message]
2013-06-24 16:25 ` Shuah Khan
2013-06-24 16:37 ` Shuah Khan
2013-06-24 16:37 ` Shuah Khan
2013-06-24 19:45 ` Rafael J. Wysocki
2013-06-24 20:38 ` Shuah Khan
2013-06-22 2:27 ` Joe Perches
2013-06-22 19:52 ` Rafael J. Wysocki
2013-06-23 1:05 ` Joe Perches
2013-06-23 9:54 ` Pavel Machek
2013-06-23 10:07 ` Rafael J. Wysocki
2013-06-23 10:03 ` Joe Perches
2013-06-23 10:22 ` Rafael J. Wysocki
2013-06-23 10:16 ` Joe Perches
2013-06-23 10:35 ` Rafael J. Wysocki
2013-06-23 10:41 ` Joe Perches
2013-06-23 11:24 ` Rafael J. Wysocki
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=7303551.DgZO2t6GUO@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=shuah.kh@samsung.com \
--cc=shuahkhan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.