linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: skelley@amperecomputing.com,
	Peter Zijlstra <peterz@infradead.org>,
	Will Deacon <will.deacon@arm.com>,
	linux-perf-users@vger.kernel.org,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Sean V Kelley <seanvk.dev@oregontracks.org>,
	Jiri Olsa <jolsa@redhat.com>, William Cohen <wcohen@redhat.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] perf vendor events arm64: Enable JSON events for eMAG
Date: Fri, 3 Aug 2018 12:48:46 -0300	[thread overview]
Message-ID: <20180803154846.GG7996@kernel.org> (raw)
In-Reply-To: <d6d9db03-657e-005c-8aa2-d0b3b41acb47@huawei.com>

Em Fri, Aug 03, 2018 at 03:41:06PM +0100, John Garry escreveu:
> On 03/08/2018 05:18, Sean V Kelley wrote:
> > This patch adds the Ampere Computing eMAG file.  This platform
> > follows the ARMv8 recommended IMPLEMENTATION DEFINED events, where
> > applicable.
> > 
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> > Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > Cc: Jiri Olsa <jolsa@redhat.com>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > Cc: John Garry <john.garry@huawei.com>
> > Cc: Will Deacon <will.deacon@arm.com>
> > Cc: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
> > Cc: William Cohen <wcohen@redhat.com>
> > 
> > Signed-off-by: Sean V Kelley <seanvk.dev@oregontracks.org>
> 
> Reviewed-by: John Garry <john.garry@huawei.com>

Thanks, applied.

- Arnaldo

      reply	other threads:[~2018-08-03 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03  4:18 [PATCH] perf vendor events arm64: Enable JSON events for eMAG Sean V Kelley
2018-08-03 14:41 ` John Garry
2018-08-03 15:48   ` Arnaldo Carvalho de Melo [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=20180803154846.GG7996@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ganapatrao.kulkarni@cavium.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=seanvk.dev@oregontracks.org \
    --cc=skelley@amperecomputing.com \
    --cc=wcohen@redhat.com \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).