[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a7bba4b9-e24e-0214-0fa7-a7f738afde25@leemhuis.info>
Date: Sat, 7 Jan 2023 08:13:32 +0100
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: Tyler Hicks <code@...icks.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Pavel Machek <pavel@...x.de>, stable@...r.kernel.org,
patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
srw@...dewatkins.net, rwarsow@....de
Subject: Re: [PATCH 6.1 000/207] 6.1.4-rc1 review
On 07.01.23 00:53, Tyler Hicks wrote:
>
> 2. Do you (or anyone else) happen to have a list of the known
> regressions? I see one specific to linux-6.1.y in the regzbot list:
>
> https://linux-regtracking.leemhuis.info/regzbot/stable/
That page only lists regressions that where introduced in stable (e.g.
say in a range like v6.1.1..v6.1.2) which might need to be handled by
the stable team (for example if a regression is caused by incomplete
backport).
All that where introduced in mainline (e.g. v6.0..v6.1) are listed on
the mainline page, as those need to be fixed in mainline by the regular
developers (e.g. never by the stable team) before they can be backported
to the stable series[1]:
https://linux-regtracking.leemhuis.info/regzbot/mainline/
There are plenty for v6.0..v6.1 currently, which is unusual, but that
can happen this time of the year. I hope the situation improves somewhat
over the next two weeks when more people are back from the holidays.
Ciao, Thorsten
[1] which is true for some of those that are introduced in the stable
series as well. That's one of the reasons why I'm not really happy with
how rezbot exposes those regressions and will improve this sooner or
later, but there are more important things on the todo list for now.
Powered by blists - more mailing lists