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,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org,
linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.12 000/230] 6.12.16-rc1 review
Date: Wed, 19 Feb 2025 14:20:09 +0100 [thread overview]
Message-ID: <2025021938-prowling-semisoft-0d2b@gregkh> (raw)
In-Reply-To: <9836adde-8d67-48b5-944b-1b9f107434a8@nvidia.com>
On Wed, Feb 19, 2025 at 01:12:41PM +0000, Jon Hunter wrote:
> Hi Greg,
>
> On 19/02/2025 13:10, Jon Hunter wrote:
> > On Wed, 19 Feb 2025 09:25:17 +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 6.12.16 release.
> > > There are 230 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 Fri, 21 Feb 2025 08:25:11 +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.12.16-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.12.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > Failures detected for Tegra ...
> >
> > Test results for stable-v6.12:
> > 10 builds: 10 pass, 0 fail
> > 26 boots: 26 pass, 0 fail
> > 116 tests: 115 pass, 1 fail
> >
> > Linux version: 6.12.16-rc1-gcf505a9aecb7
> > 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
> >
> > Test failures: tegra186-p2771-0000: pm-system-suspend.sh
>
>
> The following appear to have crept in again ...
>
> Juri Lelli <juri.lelli@redhat.com>
> sched/deadline: Check bandwidth overflow earlier for hotplug
>
> Juri Lelli <juri.lelli@redhat.com>
> sched/deadline: Correctly account for allocated bandwidth during hotplug
Yes, but all of them are there this time. Are you saying none should be
there? Does 6.14-rc work for you with these targets?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-19 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250219082601.683263930@linuxfoundation.org>
2025-02-19 13:10 ` [PATCH 6.12 000/230] 6.12.16-rc1 review Jon Hunter
2025-02-19 13:12 ` Jon Hunter
2025-02-19 13:20 ` Greg Kroah-Hartman [this message]
2025-02-19 13:32 ` Jon Hunter
2025-02-19 13:55 ` Holger Hoffstätte
2025-02-19 14:04 ` Jon Hunter
2025-02-20 10:34 ` 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=2025021938-prowling-semisoft-0d2b@gregkh \
--to=gregkh@linuxfoundation.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=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