From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Yan, Zheng" <zheng.z.yan@intel.com>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
acme@infradead.org, eranian@google.com, andi@firstfloor.org
Subject: Re: [PATCH 2/4] hrtimer: export __hrtimer_start_range_ns
Date: Wed, 19 Mar 2014 10:58:29 +0100 [thread overview]
Message-ID: <20140319095829.GG27632@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1403191053220.18573@ionos.tec.linutronix.de>
On Wed, Mar 19, 2014 at 10:53:34AM +0100, Thomas Gleixner wrote:
> On Wed, 19 Mar 2014, Peter Zijlstra wrote:
>
> > On Tue, Mar 18, 2014 at 04:56:42PM +0800, Yan, Zheng wrote:
> > > export __hrtimer_start_range_ns() to allow building perf Intel uncore
> > > driver as module
> >
> > Bah; you didn't cc the hrtimer maintainer.
> >
> > Thomas, ack on this?
>
> Yup.
Thanks!
next prev parent reply other threads:[~2014-03-19 9:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 8:56 [PATCH 1/4] perf: allow building PMU driver as module Yan, Zheng
2014-03-18 8:56 ` [PATCH 2/4] hrtimer: export __hrtimer_start_range_ns Yan, Zheng
2014-03-19 8:47 ` Peter Zijlstra
2014-03-19 9:53 ` Thomas Gleixner
2014-03-19 9:58 ` Peter Zijlstra [this message]
2014-04-18 13:08 ` [tip:perf/core] hrtimer: Export __hrtimer_start_range_ns() tip-bot for Yan, Zheng
2014-03-18 8:56 ` [PATCH 3/4] perf/x86: export perf_assign_events Yan, Zheng
2014-04-18 13:08 ` [tip:perf/core] perf/x86: Export perf_assign_events() tip-bot for Yan, Zheng
2014-03-18 8:56 ` [PATCH 4/4] perf/x86/uncore: modularize Intel uncore driver Yan, Zheng
2014-03-19 8:49 ` Peter Zijlstra
2014-03-19 11:32 ` Ingo Molnar
2014-03-19 11:42 ` Peter Zijlstra
2014-03-19 11:53 ` Ingo Molnar
2014-03-19 12:44 ` Peter Zijlstra
2014-03-19 12:55 ` Ingo Molnar
2014-03-20 15:01 ` Vince Weaver
2014-03-20 15:50 ` Andi Kleen
2014-04-18 13:08 ` [tip:perf/core] perf: Allow building PMU drivers as modules tip-bot for Yan, Zheng
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=20140319095829.GG27632@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=zheng.z.yan@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