From: Jon Hunter <jonathanh@nvidia.com>
To: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Francesco Dolcini <francesco@dolcini.it>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
rwarsow@gmx.de, conor@kernel.org, hargar@microsoft.com,
achill@achill.org, sr@sladewatkins.com,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 6.1 000/634] 6.1.160-rc1 review
Date: Sat, 10 Jan 2026 12:50:49 +0000 [thread overview]
Message-ID: <c019d930-d565-449e-bfcd-a4a5ea3a7b0d@nvidia.com> (raw)
In-Reply-To: <aWI43lUAfpKZWSx3@sirena.co.uk>
On 10/01/2026 11:32, Mark Brown wrote:
> On Sat, Jan 10, 2026 at 11:23:20AM +0000, Mark Brown wrote:
>
>> I'm also seeing bisects of similar boot failures pointing to the same
>> commit on at least i.MX8MP-EVK and Libretech Potato. Bisect log for the
>> board Francesco originally reported, the others all look the same:
>
> Pine64 Plus, Aveneger 96 and Libretech Tritium are also affected.
This is impacting some Tegra boards too.
Jon
--
nvpublic
next parent reply other threads:[~2026-01-10 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260109112117.407257400@linuxfoundation.org>
[not found] ` <20260110084142.GA6242@francesco-nb>
[not found] ` <2026011010-parasitic-delicacy-ef5e@gregkh>
[not found] ` <aWI2qATUQXAW-Bxx@sirena.co.uk>
[not found] ` <aWI43lUAfpKZWSx3@sirena.co.uk>
2026-01-10 12:50 ` Jon Hunter [this message]
2026-01-10 13:50 ` [PATCH 6.1 000/634] 6.1.160-rc1 review Greg Kroah-Hartman
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=c019d930-d565-449e-bfcd-a4a5ea3a7b0d@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=francesco@dolcini.it \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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