mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: acme@kernel.org, jolsa@kernel.org, adrian.hunter@intel.com,
	irogers@google.com, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	akanksha@linux.ibm.com, maddy@linux.ibm.com, kjain@linux.ibm.com,
	disgoel@linux.vnet.ibm.com, hbathini@linux.ibm.com
Subject: Re: [PATCH] tools/perf/tests: Remove duplicate evlist__delete in tests/tool_pmu.c
Date: Wed, 16 Oct 2024 18:00:12 +0530	[thread overview]
Message-ID: <D96F2226-12DA-4087-802B-74B347BFE43B@linux.vnet.ibm.com> (raw)
In-Reply-To: <172892779762.897882.10648635927487710641.b4-ty@kernel.org>



> On 14 Oct 2024, at 11:13 PM, Namhyung Kim <namhyung@kernel.org> wrote:
> 
> On Sun, 13 Oct 2024 22:37:32 +0530, Athira Rajeev wrote:
> 
>> The testcase for tool_pmu failed in powerpc as below:
>> 
>> ./perf test -v "Parsing without PMU name"
>>  8: Tool PMU                                                        :
>>  8.1: Parsing without PMU name                                      : FAILED!
>> 
>> This happens when parse_events results in either skip or fail
>> of an event. Because the code invokes evlist__delete(evlist)
>> and "goto out".
>> 
>> [...]
> 
> Applied to perf-tools-next, thanks!

Thanks Namhyung for picking the change

Athira
> 
> Best regards,
> Namhyung
> 
> 


      reply	other threads:[~2024-10-16 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13 17:07 Athira Rajeev
2024-10-14 17:43 ` Namhyung Kim
2024-10-16 12:30   ` Athira Rajeev [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=D96F2226-12DA-4087-802B-74B347BFE43B@linux.vnet.ibm.com \
    --to=atrajeev@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=akanksha@linux.ibm.com \
    --cc=disgoel@linux.vnet.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=namhyung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®