From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linux OMAP <linux-omap@vger.kernel.org>,
Linux Stable <stable@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: 6.1.y Regression found on AM3517
Date: Tue, 12 Sep 2023 13:14:39 +0200 [thread overview]
Message-ID: <be21241b-7f59-419b-823f-a6d66adacc87@leemhuis.info> (raw)
In-Reply-To: <CAHCN7xJo=pJkcChHm9AsNQGCJuHXgpRKKRK9ckEwdk3U-41ukw@mail.gmail.com>
[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@atomide.com> wrote:
>> * Bagas Sanjaya <bagasdotme@gmail.com> [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.
prev parent reply other threads:[~2023-09-12 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHCN7xJjK=BaNHa=+OKzOmFtNRYKX_APTp5Zj3g-X_iQcpyK6g@mail.gmail.com>
2023-09-05 0:31 ` 6.1.y Regression found on AM3517 Bagas Sanjaya
2023-09-05 6:17 ` Tony Lindgren
2023-09-06 10:59 ` Adam Ford
2023-09-12 11:14 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be21241b-7f59-419b-823f-a6d66adacc87@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).