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: "Jin, Yao" <yao.jin@linux.intel.com>,
	peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
	jolsa@redhat.com, namhyung@kernel.org, kjain@linux.ibm.com,
	alexander.shishkin@linux.intel.com, irogers@google.com,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf pmu: Fix alias matching
Date: Tue, 27 Jul 2021 13:25:29 -0300	[thread overview]
Message-ID: <YQAzeQ3IP4uAyv4L@kernel.org> (raw)
In-Reply-To: <df5e5893-08ba-1fb5-b92a-921b32ed3b2f@huawei.com>

Em Tue, Jul 27, 2021 at 11:32:55AM +0100, John Garry escreveu:
> On 21/07/2021 04:07, Jin, Yao wrote:
> > > 
> 
> Hi Arnaldo,
> 
> Can you kindly consider picking up this patch?
> 
> Thanks
> 
> > > Fixes: c47a5599eda3 ("perf tools: Fix pattern matching for same
> > > substring in different PMU type")
> > > Signed-off-by: John Garry <john.garry@huawei.com>
> > > ---
> > > @Jin Yao, please test for your scenarios
> > > 
> > 
> > For x86, the form uncore_pmu_{digits} or the uncore_pmu itself are
> > supported. We don't have more complex case such as the name in the form
> > aaa_bbbX_cccY. So my test didn't cover that complex form.
> > 
> > For my test, your patch works, thanks! :)
> 
> Can we take this as a tested-by?

Processed and added his Tested-by.

- Arnaldo

      reply	other threads:[~2021-07-27 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 15:10 [PATCH] perf pmu: Fix alias matching John Garry
2021-07-21  3:07 ` Jin, Yao
2021-07-21  7:37   ` John Garry
2021-07-27 10:32   ` John Garry
2021-07-27 16:25     ` 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=YQAzeQ3IP4uAyv4L@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=yao.jin@linux.intel.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).