linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: kan.liang@linux.intel.com, acme@kernel.org, mingo@redhat.com,
	peterz@infradead.org, irogers@google.com, namhyung@kernel.org,
	jolsa@kernel.org, adrian.hunter@intel.com,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ak@linux.intel.com, eranian@google.com, ahmad.yasin@intel.com
Subject: Re: [PATCH V4 5/5] perf vendor events arm64: Add default tags for Hisi hip08 L1 metrics
Date: Fri, 16 Jun 2023 14:48:08 +0100	[thread overview]
Message-ID: <d92494e1-37e2-36d6-6edd-a2f1093f63b9@oracle.com> (raw)
In-Reply-To: <20230616031420.3751973-6-kan.liang@linux.intel.com>

On 16/06/2023 04:14, kan.liang@linux.intel.com wrote:
> From: Kan Liang<kan.liang@linux.intel.com>
> 
> Add the default tags for Hisi hip08 as well.
> 
> Signed-off-by: Kan Liang<kan.liang@linux.intel.com>
> Cc: John Garry<john.g.garry@oracle.com>

Reviewed-by: John Garry <john.g.garry@oracle.com>

  parent reply	other threads:[~2023-06-16 13:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  3:14 [PATCH V4 0/5] New metricgroup output in perf stat default mode kan.liang
2023-06-16  3:14 ` [PATCH V4 1/5] perf metrics: Sort the Default metricgroup kan.liang
2023-06-16  5:48   ` Ian Rogers
2023-06-16  3:14 ` [PATCH V4 2/5] perf stat: New metricgroup output for the default mode kan.liang
2023-06-16  5:56   ` Ian Rogers
2023-06-16 13:23     ` Liang, Kan
2023-06-16  3:14 ` [PATCH V4 3/5] perf test: Move all the check functions of stat csv output to lib kan.liang
2023-06-16  3:14 ` [PATCH V4 4/5] perf test: Add test case for the standard perf stat output kan.liang
2023-06-16  3:14 ` [PATCH V4 5/5] perf vendor events arm64: Add default tags for Hisi hip08 L1 metrics kan.liang
2023-06-16  5:57   ` Ian Rogers
2023-06-16 13:48   ` John Garry [this message]
2023-06-16  5:59 ` [PATCH V4 0/5] New metricgroup output in perf stat default mode Ian Rogers
2023-06-16 13:26   ` Liang, Kan
2023-06-16 13:39     ` 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=d92494e1-37e2-36d6-6edd-a2f1093f63b9@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ahmad.yasin@intel.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 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).