[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180228090737.tw2m7qtmukyysllc@intel.com>
Date: Wed, 28 Feb 2018 17:07:38 +0800
From: "Du, Changbin" <changbin.du@...el.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Cc: "Du, Changbin" <changbin.du@...el.com>,
Steven Rostedt <rostedt@...dmis.org>, mingo@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] tracing/power: Polish the tracepoints cpu_idle and
cpu_frequency
On Wed, Feb 28, 2018 at 10:14:41AM +0100, Rafael J. Wysocki wrote:
> 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@...el.com> wrote:
> > >
> > > > > From the tracing perspective:
> > > > >
> > > > > Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.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@...r.kernel.org with a CC to me and I
> will take care of them.
>
sure~
> Thanks,
> Rafael
>
--
Thanks,
Changbin Du
Powered by blists - more mailing lists