public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: 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, broonie@kernel.org,
	achill@achill.org, linux-tegra@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 6.1 000/196] 6.1.156-rc1 review
Date: Wed, 15 Oct 2025 10:42:02 +0200	[thread overview]
Message-ID: <2025101540-suffix-paralyses-41b7@gregkh> (raw)
In-Reply-To: <046f08cb-0610-48c9-af24-4804367df177@nvidia.com>

On Tue, Oct 14, 2025 at 02:11:33PM +0100, Jon Hunter wrote:
> Hi Greg,
> 
> On 14/10/2025 14:09, Jon Hunter wrote:
> > On Mon, 13 Oct 2025 16:42:53 +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 6.1.156 release.
> > > There are 196 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > > 
> > > Responses should be made by Wed, 15 Oct 2025 14:42:41 +0000.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > > 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.156-rc1.gz
> > > or in the git tree and branch at:
> > > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > > and the diffstat can be found below.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > Failures detected for Tegra ...
> > 
> > Test results for stable-v6.1:
> >      10 builds:	10 pass, 0 fail
> >      28 boots:	28 pass, 0 fail
> >      119 tests:	118 pass, 1 fail
> > 
> > Linux version:	6.1.156-rc1-gb9f52894e35f
> > Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
> >                  tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000,
> >                  tegra194-p3509-0000+p3668-0000, tegra20-ventana,
> >                  tegra210-p2371-2180, tegra210-p3450-0000,
> >                  tegra30-cardhu-a04
> > 
> > Test failures:	tegra194-p2972-0000: boot.py
> 
> 
> A new kernel warning is observed for this update which is ...
> 
>  ERR KERN Early cacheinfo failed, ret = -22
> 
> Bisect is pointing to this commit ...
> 
> # first bad commit: [988121168f4a3211c7f5e561c24bb0bbe8504565]
> arch_topology: Build cacheinfo from primary CPU

Thanks for the info, I'll go drop this whole series from the tree now,
and report this to the submitter and cc: you on it.

greg k-h

  reply	other threads:[~2025-10-15  8:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 14:42 [PATCH 6.1 000/196] 6.1.156-rc1 review Greg Kroah-Hartman
2025-10-13 16:37 ` Florian Fainelli
2025-10-13 17:06 ` Brett A C Sheffield
2025-10-13 23:02 ` Peter Schneider
2025-10-14  8:47 ` Pavel Machek
2025-10-14 13:09 ` Jon Hunter
2025-10-14 13:11   ` Jon Hunter
2025-10-15  8:42     ` Greg Kroah-Hartman [this message]
2025-10-14 14:07 ` Ron Economos
2025-10-14 14:10 ` Naresh Kamboju
2025-10-14 18:00 ` Shuah Khan
2025-10-14 18:01 ` Miguel Ojeda
2025-10-16  0:05 ` Hardik Garg

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=2025101540-suffix-paralyses-41b7@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.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=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