[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <170621898549.3227482.15120591332128691529.b4-ty@kernel.org>
Date: Thu, 25 Jan 2024 13:45:01 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: James Clark <james.clark@....com>,
linux-perf-users@...r.kernel.org,
irogers@...gle.com
Cc: linux-kernel@...r.kernel.org,
Spoorthy S <spoorts2@...ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Kajol Jain <kjain@...ux.ibm.com>,
Mark Rutland <mark.rutland@....com>,
Jiri Olsa <jolsa@...nel.org>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH 0/2] perf test: Skip test_arm_callgraph_fp.sh if unwinding isn't built in
On Tue, 23 Jan 2024 16:39:00 +0000, James Clark wrote:
> The first commit outputs the unwinding feature definition in perf
> version so that the script can gate on it. And then skip the test if
> it's not present.
>
> I didn't add any fixes tags because it's modifying the perf version
> output, requires both commits, and it's just for a test skip change so
> I don't think backporting makes sense.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
--
Namhyung Kim <namhyung@...nel.org>
Powered by blists - more mailing lists