From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: "patches@lists.linux.dev" <patches@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"shuah@kernel.org" <shuah@kernel.org>,
"patches@kernelci.org" <patches@kernelci.org>,
"lkft-triage@lists.linaro.org" <lkft-triage@lists.linaro.org>,
"pavel@denx.de" <pavel@denx.de>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"sudipm.mukherjee@gmail.com" <sudipm.mukherjee@gmail.com>,
"srw@sladewatkins.net" <srw@sladewatkins.net>,
"rwarsow@gmx.de" <rwarsow@gmx.de>,
"conor@kernel.org" <conor@kernel.org>,
"allen.lkml@gmail.com" <allen.lkml@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 5.10 000/350] 5.10.224-rc2 review
Date: Sat, 17 Aug 2024 09:43:28 +0200 [thread overview]
Message-ID: <2024081757-single-anime-67a3@gregkh> (raw)
In-Reply-To: <DM8PR12MB5447F590697190728874B64FD9812@DM8PR12MB5447.namprd12.prod.outlook.com>
On Fri, Aug 16, 2024 at 08:12:36PM +0000, Jon Hunter wrote:
>
> ________________________________
> From: Jon Hunter <jonathanh@nvidia.com>
> Sent: Friday, August 16, 2024 2:43 PM
> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>; patches@lists.linux.dev <patches@lists.linux.dev>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>; torvalds@linux-foundation.org <torvalds@linux-foundation.org>; akpm@linux-foundation.org <akpm@linux-foundation.org>; linux@roeck-us.net <linux@roeck-us.net>; shuah@kernel.org <shuah@kernel.org>; patches@kernelci.org <patches@kernelci.org>; lkft-triage@lists.linaro.org <lkft-triage@lists.linaro.org>; pavel@denx.de <pavel@denx.de>; Jon Hunter <jonathanh@nvidia.com>; f.fainelli@gmail.com <f.fainelli@gmail.com>; sudipm.mukherjee@gmail.com <sudipm.mukherjee@gmail.com>; srw@sladewatkins.net <srw@sladewatkins.net>; rwarsow@gmx.de <rwarsow@gmx.de>; conor@kernel.org <conor@kernel.org>; allen.lkml@gmail.com <allen.lkml@gmail.com>; broonie@kernel.org <broonie@kernel.org>; linux-tegra@vger.kernel.org <linux-tegra@vger.kernel.org>; stable@vger.kernel.org <stable@vger.kernel.org>
> Subject: Re: [PATCH 5.10 000/350] 5.10.224-rc2 review
>
> On Fri, 16 Aug 2024 12:22:05 +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.224 release.
> > There are 350 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 Sun, 18 Aug 2024 10:14:04 +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/v5.x/stable-review/patch-5.10.224-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Failures detected for Tegra ...
>
> Test results for stable-v5.10:
> 10 builds: 10 pass, 0 fail
> 31 boots: 26 pass, 5 fail
> 45 tests: 44 pass, 1 fail
>
> Linux version: 5.10.224-rc2-g470450f8c61c
> Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
> tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
> tegra20-ventana, tegra210-p2371-2180,
> tegra210-p3450-0000, tegra30-cardhu-a04
>
> Boot failures: tegra186-p2771-0000, tegra210-p2371-2180,
> tegra210-p3450-0000
>
> Test failures: tegra194-p2972-0000: boot.py
>
> ---
>
> Apologies for the mail formatting. I am travelling and only have outlook for mobile :-(
>
> Bisect points to the following commit ...
>
> # first bad commit: [4bade5a6b1cfe81c9777aa3c8823009ff28a6e7f] memory: fsl_ifc: Make FSL_IFC config visible and selectable
>
> Reverting this does fix the issue. Seems odd but this appears to disable CONFIG_MEMORY for v5.10 with ARM64 defconfig. So something we need to fix.
Ah, that's a mess. I'll go drop this one for now, glad it's not showing
up on 5.15.y where this commit also is. It's not really important for
5.10.y so there's no harm in removing it.
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-17 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 10:22 [PATCH 5.10 000/350] 5.10.224-rc2 review Greg Kroah-Hartman
2024-08-16 14:43 ` Mark Brown
2024-08-16 19:34 ` Pavel Machek
2024-08-16 19:43 ` Jon Hunter
[not found] ` <DM8PR12MB5447F590697190728874B64FD9812@DM8PR12MB5447.namprd12.prod.outlook.com>
2024-08-17 7:43 ` Greg Kroah-Hartman [this message]
2024-08-16 23:12 ` Florian Fainelli
2024-08-17 5:57 ` Anders Roxell
2024-08-17 7:46 ` 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=2024081757-single-anime-67a3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.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=srw@sladewatkins.net \
--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