The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: "Du, Changbin" <changbin.du@intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing/power: Polish the tracepoints cpu_idle and cpu_frequency
Date: Wed, 28 Feb 2018 10:14:41 +0100	[thread overview]
Message-ID: <fe962a88-af96-ed34-48c2-49f5e45375a7@intel.com> (raw)
In-Reply-To: <20180228024502.6kgudpsvx7hvlvcn@intel.com>

On 2/28/2018 3:45 AM, Du, Changbin wrote:
> On Tue, Feb 27, 2018 at 05:39:38PM -0500, Steven Rostedt wrote:
>> On Tue, 27 Feb 2018 17:35:27 +0800
>> "Du, Changbin" <changbin.du@intel.com> wrote:
>>
>>>>  From the tracing perspective:
>>>>
>>>> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
>>>>
>>>> -- Steve
>>>>   
>>> Hi Steve, will you pick this or someoneelse?
>> I maintain the tracing infrastructure, but the tracing use cases are
>> maintained by the maintainers of the users of the trace events. That
>> is, who added these trace events? They are the ones most affected by
>> these changes.
>>
>> For example, it looks like Rafael J. Wysocki, is the one that added
>> trace_cpu_frequency(). He's the one that is affected by this change,
>> and is the one that you need to have take it.
>>
> Got it, thanks!
>
> Hi Wysocki, could you take a look?

Please send the patch(es) to linux-pm@vger.kernel.org with a CC to me 
and I will take care of them.

Thanks,
Rafael

  reply	other threads:[~2018-02-28  9:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1518576038-16198-1-git-send-email-changbin.du@intel.com>
2018-02-14 15:19 ` [PATCH v2] tracing/power: Polish the tracepoints cpu_idle and cpu_frequency Steven Rostedt
     [not found] ` <20180214095440.2debdbba@gandalf.local.home>
     [not found]   ` <20180227093526.z7gxg2nk7xmfk2oi@intel.com>
     [not found]     ` <20180227173938.0826ed9b@vmware.local.home>
2018-02-28  2:45       ` Du, Changbin
2018-02-28  9:14         ` Rafael J. Wysocki [this message]
2018-02-28  9:07           ` Du, Changbin
     [not found] <1519809638-24248-1-git-send-email-changbin.du@intel.com>
     [not found] ` <CAJZ5v0jqG0pcqOuvAVoP7sNKoOe+3ByMk4X5AZASp84OPcrgPg@mail.gmail.com>
     [not found]   ` <20180301022719.xyfcu5tpmadjxbut@intel.com>
2018-03-02  9:24     ` Rafael J. Wysocki
2018-03-02  9:41       ` Du, Changbin
2018-03-02 10:18         ` Rafael J. Wysocki
2018-03-02 10:15           ` Du, Changbin
2018-03-02 10:39             ` Rafael J. Wysocki
2018-03-02 10:50               ` Du, Changbin

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=fe962a88-af96-ed34-48c2-49f5e45375a7@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=changbin.du@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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