On 21.04.22 18:07, Thorsten Leemhuis wrote:
On 20.04.22 00:02, Linus Walleij wrote:
On Mon, Apr 18, 2022 at 6:34 AM Mario Limonciello mario.limonciello@amd.com wrote:
Linus Walleij,
As this is backported to 5.15.y, 5.16.y, 5.17.y and those all had point releases a bunch of people are hitting it now. If you choose to adopt this patch instead of revert the broken one, you can add to the commit message too:
I am on parental leave kind of, but Bartosz knows what to do, in this case, since it is ACPI-related, Andy knows best what to do, and I see he also replied.
Bartosz, Andy, what's the status here? It looks like the patch didn't make any progress in the past few days (or did I miss it?). I'd really like to see this patch or a revert of 5467801f1fcb ("gpio: Restrict usage of GPIO chip irq members before initialization") mainlined by rc4, so Greg (CCed) can fix it in the next round of stable updates, as it seems quite a few people are affected by the problem.
Mario, are you aware if this patch made any progress towards getting merged? If not, I wonder if we (you?) maybe should ask Linus to pick this up directly giving the circumstances to speed things up (or maybe a v2 that incorporates all the Reviewed-by/ACKs that accumulated).
Ciao, Thorsten
Reminder: this is one of those issue that we IMHO really should fix quickly, as explained by a text recently added to the documentation:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Docu...
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.