[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 06.09.23 12:59, Adam Ford wrote:
> On Tue, Sep 5, 2023 at 11:25 AM Tony Lindgren <tony@xxxxxxxxxxx> wrote:
>> * Bagas Sanjaya <bagasdotme@xxxxxxxxx> [230905 00:31]:
>>> On Mon, Sep 04, 2023 at 11:37:46AM -0500, Adam Ford wrote:
>>>> I have an AM3517-EVM board that I am trying to use the latest 6.1.y
>>>> stable, currently 6.1.51.
>>>>
>>>> With git bisect, I narrowed the regression between 6.1.15 and 6.1.16 to commit
>>>> eaf9b5612a47 ("driver core: fw_devlink: Don't purge child fwnode's
>>>> consumer links")
>>>>
>>>> In the regression, 48002000.scm appears as not ready. This affects a
>>>> variety of dependent peripherals making them unavailable:
> [...]
> Indeed, it does appear that a patch was missing from the back-ported series.
>
> Applying commit 4a032827daa8 ("of: property: Simplify
> of_link_to_phandle()") to the 6.1.y branch appears
> to fix the regression.
>
> Thanks for the pointer to the series.
>
> Stable group,
>
> Do I need to send a separate e-mail requesting the backporting of that
> commit to the 6.1.y branch?
Stable team picked this up, hence:
#regzbot fix: of: property: Simplify of_link_to_phandle()
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
