From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
mingo@redhat.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, namhyung@kernel.org,
ganapatrao.kulkarni@cavium.com, zhangshaokun@hisilicon.com,
yao.jin@linux.intel.com, will.deacon@arm.com, ak@linux.intel.com,
agustinv@codeaurora.org
Subject: Re: [V5 PATCH] perf parse-events: Specially handle uncore event alias in small groups
Date: Mon, 7 May 2018 15:40:02 -0300 [thread overview]
Message-ID: <20180507184002.GB13491@kernel.org> (raw)
In-Reply-To: <20180507183930.GA13491@kernel.org>
Em Mon, May 07, 2018 at 03:39:30PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, May 04, 2018 at 03:21:16PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Fri, May 04, 2018 at 01:57:33PM -0400, Liang, Kan escreveu:
> > > On 5/1/2018 12:33 PM, Jiri Olsa wrote:
> > > > Acked-by: Jiri Olsa <jolsa@kernel.org>
> > > Are you OK with the patch?
> > > It looks like Jirka has another patch which will touch the same code.
> > > If it's OK for you, could you please merge the patch? So he can do the
> > > changes on top of this patch.
> > Yeah, I'm applying to my perf/core branch and pushing it out now.
> So, this will probably break when merging with perf/urgent due to the
> revert of a patch that touches the parser files, just a heads out.
s/heads out/heads up/
:-)
-Arnaldo
next prev parent reply other threads:[~2018-05-07 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 14:31 [V5 PATCH] perf parse-events: Specially handle uncore event alias in small groups kan.liang
2018-05-01 16:33 ` Jiri Olsa
2018-05-04 17:57 ` Liang, Kan
2018-05-04 18:21 ` Arnaldo Carvalho de Melo
2018-05-07 18:39 ` Arnaldo Carvalho de Melo
2018-05-07 18:40 ` Arnaldo Carvalho de Melo [this message]
2018-05-07 19:06 ` Liang, Kan
2018-05-07 19:07 ` Arnaldo Carvalho de Melo
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=20180507184002.GB13491@kernel.org \
--to=acme@kernel.org \
--cc=agustinv@codeaurora.org \
--cc=ak@linux.intel.com \
--cc=ganapatrao.kulkarni@cavium.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
--cc=yao.jin@linux.intel.com \
--cc=zhangshaokun@hisilicon.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 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.