From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: REGRESSION linux-next since Nov 16th, perf tool broken (at least on s390)
Date: Thu, 30 Nov 2023 15:16:10 +0100 [thread overview]
Message-ID: <63da0e45-12b4-4ab4-b66c-9fadf8251ee1@leemhuis.info> (raw)
In-Reply-To: <ZV22eWivHWOkKxGB@archie.me>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 22.11.23 09:06, Bagas Sanjaya wrote:
> On Wed, Nov 22, 2023 at 08:38:28AM +0100, Thomas Richter wrote:
>> perf tool fails on linux-next since Nov 16th on s390 when invoking perf on
>> any PMU event, as in
>
> #regzbot ^introduced: 652ffc2104ec1f
> #regzbot title: event syntax error due to narrow startup race fix
Bagas, I currently lack resources to handle regressions in next, please
don't add them, for the foreseeable future that's not worth the trouble.
#regzbot fix: perf: Fix the nr_addr_filters fix
#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.
prev parent reply other threads:[~2023-11-30 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aca1eb79-5dee-4634-8727-eebb251c9e1e@linux.ibm.com>
2023-11-22 8:06 ` REGRESSION linux-next since Nov 16th, perf tool broken (at least on s390) Bagas Sanjaya
2023-11-30 14:16 ` Linux regression tracking #update (Thorsten Leemhuis) [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=63da0e45-12b4-4ab4-b66c-9fadf8251ee1@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).