[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <984f4eb8-2d47-45ad-184f-7f5637820101@leemhuis.info>
Date: Tue, 20 Jun 2023 14:38:36 +0200
From: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Ravi Bangoria <ravi.bangoria@....com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>
Cc: mark.rutland@....com, jolsa@...nel.org, irogers@...gle.com,
bp@...en8.de, adrian.hunter@...el.com,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Subject: Re: [REGRESSION][BISECT] perf/core: Remove pmu linear searching code
[TLDR: This mail in primarily relevant for Linux regression tracking. A
change or fix related to the regression discussed in this thread was
posted or applied, but it did not use a Closes: tag to point to the
report, as Linus and the documentation call for. Things happen, no
worries -- but now the regression tracking bot needs to be told manually
about the fix. See link in footer if these mails annoy you.]
On 04.06.23 13:38, Krzysztof Kozlowski wrote:
>
> #regzbot introduced: 9551fbb64d09
>
> Bisect pointed to commit 9551fbb64d09 ("perf/core: Remove pmu linear
> searching code") as first one where all hardware events are gone from
> perf for ARMv7 Exynos5422 board.
#regzbot fix: 228020b490eda91
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
Powered by blists - more mailing lists