From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Joe Perches <joe@perches.com>
Cc: Shuah Khan <shuah.kh@samsung.com>,
pavel@ucw.cz, len.brown@intel.com, gregkh@linuxfoundation.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
shuahkhan@gmail.com
Subject: Re: [PATCHv v3] power: Include additional information in pm_print_times
Date: Sun, 23 Jun 2013 12:35:31 +0200 [thread overview]
Message-ID: <2722061.UXbT4p7DY0@vostro.rjw.lan> (raw)
In-Reply-To: <1371982590.3137.32.camel@joe-AO722>
On Sunday, June 23, 2013 03:16:30 AM Joe Perches wrote:
> On Sun, 2013-06-23 at 12:22 +0200, Rafael J. Wysocki wrote:
> > On Sunday, June 23, 2013 03:03:31 AM Joe Perches wrote:
> > > On Sun, 2013-06-23 at 12:07 +0200, Rafael J. Wysocki wrote:
> > > > On Saturday, June 22, 2013 06:05:50 PM Joe Perches wrote:
> > > > > If any script needs something stable it should
> > > > > depend on information available through other
> > > > > sources like trace or proc or sysfs.
> > > >
> > > > That is clearly impossible in this particular case, though.
> > >
> > > Why couldn't this printk be converted into an equivalent tracepoint?
> >
> > Well, why wouldn't you try to do that?
>
> Why should I?
Because you're arguing that it should be done.
If you think that it's better to use tracepoints here, please implement those
tracepoints and show everyone that they are really better than what we have.
Till then, we'll use what's already there.
Thanks,
Rafael
next prev parent reply other threads:[~2013-06-23 10:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 19:36 Shuah Khan
2013-06-17 19:41 ` Greg KH
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
2013-06-24 16:25 ` 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 [this message]
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=2722061.UXbT4p7DY0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®