From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Michael Petlan <mpetlan@redhat.com>
Cc: Jakub Brnak <jbrnak@redhat.com>,
acme@redhat.com, linux-perf-users@vger.kernel.org,
namhyung@kernel.org, irogers@google.com
Subject: Re: [PATCH v5 0/7] Introduce structure for shell tests
Date: Fri, 23 Jan 2026 13:29:51 -0300 [thread overview]
Message-ID: <aXOh_4oN9P_Sxo8t@x1> (raw)
In-Reply-To: <a5f59c64-0da-6928-7a9-c5b6c2be8ef8@redhat.com>
On Fri, Jan 23, 2026 at 03:26:54PM +0100, Michael Petlan wrote:
> Hello Ian and Namhyung,
>
> kindly reminding this patchset. Could we get it merged soon please?
> Or is there still anything to address?
>
> Thanks in advance!
Just test applied and it went cleanly, will try to review it after
lunch.
- Arnaldo
> Regards,
> Michael
>
> On Tue, 25 Nov 2025, Jakub Brnak wrote:
> > Hi maintainers,
> >
> > This revision of series of patches continues the effort of upstreaming a perftool-testsuite and
> > incorporates the review feedback that was previously discussed.
> > A new patch (7/7) was added to fix the incorrect relative path for locating stderr-whitelist.txt
> > in report tests.
> >
> > Thanks,
> > Jakub
> >
> > Link to v4: https://lore.kernel.org/linux-perf-users/20250930160923.13728-1-jbrnak@redhat.com/#t
> >
> > Changes since v4:
> > Patch 1: applied review feedback, renamed shell_info -> shell_test_info, minor cleanups
> > Patch 2: renamed shell_info -> shell_test_info
> > Patch 4: renamed shell_info -> shell_test_info
> > Patch 7: added in v5, fix for relative path to
> > stderr-whitelist.txt in report tests
> >
> > Jakub Brnak (7):
> > perf tests: Create a structure for shell tests
> > perf test: Provide setup for the shell test suite
> > perftool-testsuite: Add empty setup for base_probe
> > perf test: Introduce storing logs for shell tests
> > perf test: Format log directories for shell tests
> > perf test: Remove perftool drivers
> > perf test: Fix relative path for 'stderr-whitelist.txt'
> >
> > tools/perf/tests/builtin-test.c | 129 +++++++-
> > tools/perf/tests/shell/base_probe/setup.sh | 13 +
> > .../tests/shell/base_report/test_basic.sh | 6 +-
> > .../tests/shell/perftool-testsuite_probe.sh | 24 --
> > .../tests/shell/perftool-testsuite_report.sh | 23 --
> > tools/perf/tests/tests-scripts.c | 288 +++++++++++++++---
> > tools/perf/tests/tests-scripts.h | 15 +
> > tools/perf/tests/tests.h | 8 +-
> > 8 files changed, 398 insertions(+), 108 deletions(-)
> > create mode 100755 tools/perf/tests/shell/base_probe/setup.sh
> > delete mode 100755 tools/perf/tests/shell/perftool-testsuite_probe.sh
> > delete mode 100755 tools/perf/tests/shell/perftool-testsuite_report.sh
> >
> > --
> > 2.51.1
> >
> >
next prev parent reply other threads:[~2026-01-23 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 15:56 [PATCH v5 0/7] Introduce structure for shell tests Jakub Brnak
2025-11-25 15:56 ` [PATCH v5 1/7] perf tests: Create a " Jakub Brnak
2026-01-23 16:51 ` Ian Rogers
2025-11-25 15:56 ` [PATCH v5 2/7] perf test: Provide setup for the shell test suite Jakub Brnak
2025-11-25 15:56 ` [PATCH v5 3/7] perftool-testsuite: Add empty setup for base_probe Jakub Brnak
2025-11-25 15:56 ` [PATCH v5 4/7] perf test: Introduce storing logs for shell tests Jakub Brnak
2026-01-23 16:57 ` Ian Rogers
2025-11-25 15:56 ` [PATCH v5 5/7] perf test: Format log directories " Jakub Brnak
2025-11-25 15:56 ` [PATCH v5 6/7] perf test: Remove perftool drivers Jakub Brnak
2025-11-25 15:56 ` [PATCH v5 7/7] perf test: Fix relative path for 'stderr-whitelist.txt' Jakub Brnak
2026-01-23 14:26 ` [PATCH v5 0/7] Introduce structure for shell tests Michael Petlan
2026-01-23 16:29 ` Arnaldo Carvalho de Melo [this message]
2026-01-23 17:02 ` Ian Rogers
2026-01-26 20:37 ` 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=aXOh_4oN9P_Sxo8t@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=jbrnak@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.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