From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Huang Rui <ray.huang@amd.com>, Ingo Molnar <mingo@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Thomas Gleixner <tglx@linutronix.de>,
Robert Richter <rric@kernel.org>,
Jacob Shin <jacob.w.shin@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Kan Liang <kan.liang@intel.com>,
linux-kernel@vger.kernel.org, spg_linux_kernel@amd.com,
x86@kernel.org,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH 0/2] perf/x86/msr: Add some new AMD performance event counters
Date: Mon, 21 Mar 2016 13:40:10 +0100 [thread overview]
Message-ID: <20160321124010.GU6344@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160321103124.GD15904@pd.tnic>
On Mon, Mar 21, 2016 at 11:31:24AM +0100, Borislav Petkov wrote:
> On Mon, Mar 21, 2016 at 06:09:31PM +0800, Huang Rui wrote:
> > Can you apply these two patches since I sent two months before. Need I
> > rebase them?
>
> Yes, please rebase and test them ontop of 4.6-rc1 once Linus releases it
> at the end of this/beginning of next week.
No need, I stomped on them and now they fit again.
prev parent reply other threads:[~2016-03-21 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 8:29 [PATCH 0/2] perf/x86/msr: Add some new AMD performance event counters Huang Rui
2016-01-29 8:29 ` [PATCH 1/2] perf/x86/msr: Add AMD performance time-stamp counter support Huang Rui
2016-03-31 9:22 ` [tip:perf/core] perf/x86/msr: Add AMD PTSC (Performance Time-Stamp Counter) support tip-bot for Huang Rui
2016-01-29 8:29 ` [PATCH 2/2] perf/x86/msr: Add AMD instructions retired performance counter Huang Rui
2016-03-31 9:22 ` [tip:perf/core] perf/x86/msr: Add AMD IRPERF (Instructions Retired) " tip-bot for Huang Rui
2016-03-21 10:09 ` [PATCH 0/2] perf/x86/msr: Add some new AMD performance event counters Huang Rui
2016-03-21 10:31 ` Borislav Petkov
2016-03-21 12:40 ` Peter Zijlstra [this message]
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=20160321124010.GU6344@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=acme@kernel.org \
--cc=bp@alien8.de \
--cc=fengguang.wu@intel.com \
--cc=jacob.w.shin@gmail.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=ray.huang@amd.com \
--cc=rric@kernel.org \
--cc=spg_linux_kernel@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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.