From: Steven Rostedt <rostedt@goodmis.org>
To: todd.e.brandt@linux.intel.com
Cc: linux-pm@vger.kernel.org, rafael.j.wysocki@intel.com, rjw@rjwysocki.net
Subject: Re: [PATCH v2] PM: trace events for suspend/resume
Date: Fri, 30 May 2014 22:36:50 -0400 [thread overview]
Message-ID: <20140530223650.62ca8471@gandalf.local.home> (raw)
In-Reply-To: <20140530223349.5f33b0fd@gandalf.local.home>
On Fri, 30 May 2014 22:33:49 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> This is assuming that all of these calls are in core kernel code and
> not in modules. Are they?
>
Reading my comment I wrote about tracepoint_string(), it's OK to be
used even with modules. As long as the strings don't change while the
module is loaded (seems to be the case for all strings here).
-- Steve
next prev parent reply other threads:[~2014-05-31 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 1:52 [PATCH v2] PM: trace events for suspend/resume Todd E Brandt
2014-05-31 2:33 ` Steven Rostedt
2014-05-31 2:36 ` Steven Rostedt [this message]
2014-05-31 2:58 ` Todd E Brandt
2014-05-31 3:07 ` Steven Rostedt
2014-06-06 6:46 ` Todd E Brandt
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=20140530223650.62ca8471@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=todd.e.brandt@linux.intel.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;
as well as URLs for NNTP newsgroup(s).