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, adrian.hunter@intel.com,
	alexander.shishkin@linux.intel.com, howardchu95@gmail.com,
	irogers@google.com, james.clark@linaro.org, jolsa@kernel.org,
	kan.liang@linux.intel.com, leo.yan@linux.dev,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	mark.rutland@arm.com, mingo@redhat.com, peterz@infradead.org,
	tmricht@linux.ibm.com, vmolnaro@redhat.com,
	weilin.wang@intel.com, zegao2021@gmail.com,
	zhaimingbing@cmss.chinamobile.com
Subject: Re: [PATCH v1 0/3] Make a "Setup struct perf_event_attr" a shell test
Date: Sun, 13 Oct 2024 11:08:23 +0530	[thread overview]
Message-ID: <DB114AFD-C80A-4789-80EC-715F7B0CC6A1@linux.vnet.ibm.com> (raw)
In-Reply-To: <20241011064824.1432562-1-namhyung@kernel.org>



> On 11 Oct 2024, at 12:18 PM, Namhyung Kim <namhyung@kernel.org> wrote:
> 
> On 2024-10-10 15:50 -0700, Namhyung Kim wrote:
>> On Tue, 01 Oct 2024 10:19:47 -0700, Ian Rogers wrote:
>>> The path detection for "Setup struct perf_event_attr" test is brittle
>>> and leads to the test frequently not running. Running shell tests is
>>> reasonably robust, so make the test a shell test. Move the test files
>>> to reflect this.
>>> 
>>> Ian Rogers (3):
>>>  perf test: Add a shell wrapper for "Setup struct perf_event_attr"
>>>  perf test: Remove C test wrapper for attr.py
>>>  perf test: Move attr files into shell directory where they are used
>>> 
>>> [...]
>> 
>> Applied to perf-tools-next, thanks!
> 
> Dropped from perf-tools-next due to build failures on PPC.
> 
> https://lore.kernel.org/r/20241011102330.02bece12@canb.auug.org.au

Hi Namhyung

I am checking this on powerpc. Will respond with the findings

Thanks
Athira
> 
> Thanks,
> Namhyung
> 


  reply	other threads:[~2024-10-13  5:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 17:19 Ian Rogers
2024-10-01 17:19 ` [PATCH v1 1/3] perf test: Add a shell wrapper for "Setup struct perf_event_attr" Ian Rogers
2024-10-01 17:19 ` [PATCH v1 2/3] perf test: Remove C test wrapper for attr.py Ian Rogers
2024-10-01 17:19 ` [PATCH v1 3/3] perf test: Move attr files into shell directory where they are used Ian Rogers
2024-10-08 18:55 ` [PATCH v1 0/3] Make a "Setup struct perf_event_attr" a shell test Ian Rogers
2024-10-09  5:38   ` Namhyung Kim
2024-10-09  5:59     ` Ian Rogers
2024-10-10  0:56       ` Namhyung Kim
2024-10-10 15:50 ` Namhyung Kim
2024-10-11  6:48   ` Namhyung Kim
2024-10-13  5:38     ` Athira Rajeev [this message]
2024-10-13  6:58       ` Athira Rajeev

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=DB114AFD-C80A-4789-80EC-715F7B0CC6A1@linux.vnet.ibm.com \
    --to=atrajeev@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=leo.yan@linux.dev \
    --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=tmricht@linux.ibm.com \
    --cc=vmolnaro@redhat.com \
    --cc=weilin.wang@intel.com \
    --cc=zegao2021@gmail.com \
    --cc=zhaimingbing@cmss.chinamobile.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

all inboxes | Powered by JetHome®