From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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/419] 6.12.14-rc2 review
Date: Fri, 14 Feb 2025 21:12:39 +0000 [thread overview]
Message-ID: <bcf76664-e77c-44b3-b78f-bcefc7aa3fc1@nvidia.com> (raw)
In-Reply-To: <57e42fbb-9372-4618-bbed-71da01326ffe@rnnvmail203.nvidia.com>
Hi Greg,
On 14/02/2025 21:11, Jon Hunter wrote:
> On Fri, 14 Feb 2025 14:58:41 +0100, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.12.14 release.
>> There are 419 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, 16 Feb 2025 13:37:21 +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.14-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-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: 107 pass, 9 fail
>
> Linux version: 6.12.14-rc2-ga58d06766300
> 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: tegra124-jetson-tk1: cpu-hotplug
> tegra124-jetson-tk1: pm-system-suspend.sh
> tegra186-p2771-0000: cpu-hotplug
> tegra20-ventana: cpu-hotplug
> tegra210-p2371-2180: cpu-hotplug
> tegra210-p3450-0000: cpu-hotplug
>
Bisect is pointing to this commit ...
# first bad commit: [3efd1a4cc13eccc1ae02b0511aec5bc74a168b74] sched/deadline: Correctly account for allocated bandwidth during hotplug
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2025-02-14 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 13:58 [PATCH 6.12 000/419] 6.12.14-rc2 review Greg Kroah-Hartman
2025-02-14 19:43 ` Slade Watkins
2025-02-14 19:59 ` Harshit Mogalapalli
2025-02-14 20:13 ` [PATCH 6.12 000/583] " Hardik Garg
2025-02-14 21:11 ` [PATCH 6.12 000/419] " Jon Hunter
2025-02-14 21:12 ` Jon Hunter [this message]
2025-02-15 7:45 ` Greg Kroah-Hartman
2025-02-15 0:56 ` Mark Brown
2025-02-15 2:05 ` Markus Reichelt
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=bcf76664-e77c-44b3-b78f-bcefc7aa3fc1@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.