[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b20b567f-ce96-45e8-aab7-29768f8313f5@leemhuis.info>
Date: Tue, 21 May 2024 12:01:17 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Laura Nao <laura.nao@...labora.com>
Cc: mika.westerberg@...ux.intel.com, linus.walleij@...aro.org, brgl@...ev.pl,
kernel@...labora.com, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-acpi@...r.kernel.org,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
"kernelci.org bot" <bot@...nelci.org>,
Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [PATCH] gpiolib: acpi: Move ACPI device NULL check to
acpi_can_fallback_to_crs()
On 13.05.24 12:02, Andy Shevchenko wrote:
> On Mon, May 13, 2024 at 11:56:10AM +0200, Laura Nao wrote:
>> Following the relocation of the function call outside of
>> __acpi_find_gpio(), move the ACPI device NULL check to
>> acpi_can_fallback_to_crs().
>
> Thank you, I'll add this to my tree as we have already the release happened.
> I will be available after v6.10-rc1 is out.
Hmm, what exactly do you mean with that? It sounds as you only want to
add this to the tree once -rc1 is out -- which seems likely at this
point, as that patch is not yet in -next. If that's the case allow me to
ask: why? I'd say it should be fixes rather sooner than later, as other
people might run into this as well and then have to deal with bisecing,
reporting, ...
Ciao, Thorsten
Powered by blists - more mailing lists