Messages in this thread | | | Date | Sat, 1 Jul 2023 16:10:57 +0200 | Subject | Re: Fwd: commit 9df9d2f0471b causes boot failure in pre-rc1 6.5 kernel | From | "Linux regression tracking (Thorsten Leemhuis)" <> |
| |
[dropping people from CC that likely don't care]
On 01.07.23 15:42, Bagas Sanjaya wrote: > On 7/1/23 19:43, Linux regression tracking #update (Thorsten Leemhuis) wrote: >> On 01.07.23 14:27, Bagas Sanjaya wrote: >>> On Wed, Jun 28, 2023 at 09:06:22PM +0700, Bagas Sanjaya wrote: >>>> I notice a regression report on Bugzilla [1]. Quoting from it: >>> [....] >>>> See Bugzilla for the full thread. >>>> >>>> #regzbot introduced: 9df9d2f0471b https://bugzilla.kernel.org/show_bug.cgi?id=217602 >>>> #regzbot title: early arch_cpu_finalize_init() cause immediate boot failure >>> #regzbot fix: 0303c9729afc40 >> >> Bagas, FWIW, there was no need for this at all. Regzbot would have >> noticed that patch automatically due to the "Link: >> https://bugzilla.kernel.org/show_bug.cgi?id=217602" in the patch >> description (thx for this, tglx) once it landed in next or mainline >> (just like it noticed >> https://lore.kernel.org/lkml/168813193932.404.2885732890333911092.tip-bot2@tip-bot2/ >> earlier). > > OK, thanks for another tip! I was doing above because at the time > regzbot doesn't mark the regression as solved, so I had to manually > told it.
regzbot could notice this sooner by monitoring all the for-linus and for-next subsystem development trees. But I'm not sure if that's worth it, because normally things that land there show up in -next within 24 hours anyway.
Ciao, Thorsten
| |