From: "Regzbot (on behalf of Thorsten Leemhuis)" <email@example.com>
To: LKML <firstname.lastname@example.org>,
Linus Torvalds <email@example.com>,
Linux regressions mailing list <firstname.lastname@example.org>
Subject: Linux regressions report for mainline [2023-03-05]
Date: Sun, 5 Mar 2023 14:33:06 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
Hi Linus. There is nothing much to report wrt to regressions,
nevertheless let me give a quick status update.
As of now I only track two afaik unfixed build problems that were
introduced this cycle. Both were reported by Guenter (he even added them
to regzbot's tracking himself, yeah!). See below for details.
Apart from those there are two more issues I don't track (yet) and only
have a loose eye on, as I had assumed the maintainers would send fixes
for them in before -rc1. But that afaics didn't happen, so let me
quickly mention the fixes here:
* media: Fix building pdfdocs
[looks like this is needed in mainline, but it's not entirely clear]
* clk: Mark a fwnode as initialized when using CLK_OF_DECLARE* macros
I also had hoped a fix for a TPM regression from the 6.1 cycle would
reach your before -rc1, as it would prevent stuttering on some Ryzen
systems that more than just a user or two currently has to deal with
(due to a hw issue that happens more often due to a change in 6.1).
That's why some of the involved developers would have liked to see the
fix merged for 6.2 already. Well, that didn't happen. Luckily that patch
since a few days is at least in Linux-next now (currently as 8699d5244e):
Hi, this is regzbot, the Linux kernel regression tracking bot.
Currently I'm aware of 2 regressions in linux-mainline. Find the
current status below and the latest on the web:
Bye bye, hope to see you soon for the next report.
Regzbot (on behalf of Thorsten Leemhuis)
current cycle (v6.2.. aka v6.2-post), culprit identified
[ *NEW* ] Build error in drivers/media/i2c/imx290.c if PM support is disabled
By Guenter Roeck; 5 days ago; 1 activities, latest 5 days ago.
Introduced in 02852c01f654
Recent activities from: Guenter Roeck (1)
[ *NEW* ] Build failures for sparc64:allmodconfig and parisc:allmodconfig with gcc 11.x+
By Guenter Roeck; 11 days ago; 4 activities, latest 8 days ago.
Introduced in 1ec49744ba83
Recent activities from: Guenter Roeck (3), David Sterba (1)
One patch associated with this regression:
* Re: [PATCH 8/8] btrfs: turn on -Wmaybe-uninitialized
10 days ago, by Guenter Roeck
End of report
All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
Thanks for your attention, have a nice day!
Regzbot, your hard working Linux kernel regression tracking robot
P.S.: Wanna know more about regzbot or how to use it to track regressions
for your subsystem? Then check out the getting started guide or the
The short version: if you see a regression report you want to see
tracked, just send a reply to the report where you Cc
firstname.lastname@example.org with a line like this:
#regzbot introduced: v5.13..v5.14-rc1
If you want to fix a tracked regression, just do what is expected
anyway: add a 'Link:' tag with the url to the report, e.g.:
reply other threads:[~2023-03-05 14:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.