From: Peter Zijlstra <peterz@infradead.org>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Paul Mackerras <paulus@samba.org>,
Andi Kleen <andi.kleen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Vince Weaver <vincent.weaver@maine.edu>
Subject: Re: [PATCH v3] perf/rapl: support per domain energy unit
Date: Wed, 15 Apr 2015 18:36:08 +0200 [thread overview]
Message-ID: <20150415163608.GY5029@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150415091923.35cc747b@icelake>
On Wed, Apr 15, 2015 at 09:19:23AM -0700, Jacob Pan wrote:
> On Wed, 15 Apr 2015 17:40:59 +0200
> Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Wed, Apr 15, 2015 at 08:08:07AM -0700, Jacob Pan wrote:
> > > Any more comments? This is really a bug fix.
> >
> > I had it queued but it missed the first pull req, I'll put it in
> > /urgent.
> Thanks, just for my learning the next time, which tree should i check
> whether these patches are taken or not. Is it in one of the tip
> branches?
You'll get a tip-commit email if it lands in tip, until that time it
sits in my quilt queue, which I might or might not push out to a git
tree -- I'm not very consistent or timely with that :/
next prev parent reply other threads:[~2015-04-15 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 21:28 [PATCH v3] perf/rapl: support per domain energy unit Jacob Pan
2015-04-06 15:21 ` Jacob Pan
2015-04-06 17:30 ` Stephane Eranian
2015-04-15 15:08 ` Jacob Pan
2015-04-15 15:40 ` Peter Zijlstra
2015-04-15 16:19 ` Jacob Pan
2015-04-15 16:36 ` Peter Zijlstra [this message]
2015-04-18 10:14 ` [tip:perf/urgent] perf/x86/intel/rapl: Fix energy counter measurements but supporing per domain energy units tip-bot for Jacob Pan
-- strict thread matches above, loose matches on Subject: below --
2015-06-15 17:32 [PATCH v3] perf/rapl: support per domain energy unit Vince Weaver
2015-06-15 20:07 ` Jacob Pan
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=20150415163608.GY5029@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=andi.kleen@intel.com \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=vincent.weaver@maine.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.