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@nabladev.com,
f.fainelli@gmail.com, sudipm.mukherjee@gmail.com, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
achill@achill.org, sr@sladewatkins.com,
linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.18 000/632] 6.18.57-rc2 review
Date: Thu, 15 Oct 2026 14:16:45 +0100 [thread overview]
Message-ID: <2a5adbe8-ed67-476b-bffd-169c8c50f686@nvidia.com> (raw)
In-Reply-To: <6d8a0529-033b-4d81-a2e8-cf735e9a4b7b@rnnvmail204.nvidia.com>
On 15/10/2026 14:13, Jon Hunter wrote:
> On Wed, 14 Oct 2026 14:50:40 +0200, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.18.57 release.
>> There are 632 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, 16 Oct 2026 12:37:22 +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.18.57-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.18.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
> Failures detected for Tegra ...
>
> Test results for stable-v6.18:
> builds: 11 pass, 0 fail
> boots: 28 pass, 0 fail
> tests: 163 pass, 1 fail
>
> Linux version: 6.18.57-rc2-gfea86ab6861e
> Boards tested: tegra20-ventana
> tegra30-cardhu-a04
> tegra124-jetson-tk1
> tegra210-p2371-2180
> tegra210-p3450-0000
> tegra186-p2771-0000
> tegra186-p3509-0000+p3636-0001
> tegra194-p2972-0000
> tegra194-p3509-0000+p3668-0000
> tegra234-p3737-0000+p3701-0000
> tegra234-p3768-0000+p3767-0005
>
> Test failures: tegra194-p2972-0000: boot.py
This is the same kernel warning reported by Peter Schneider.
WARNING KERN Driver 'ufs_device_wlun' needs updating - please use bus_type methods
Jon
--
nvpublic
prev parent reply other threads:[~2026-10-15 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 12:50 Greg Kroah-Hartman
2026-10-14 13:20 ` Brett A C Sheffield
2026-10-14 19:34 ` Peter Schneider
2026-10-14 22:33 ` Sasha Levin
2026-10-15 10:27 ` Jon Hunter
2026-10-14 21:18 ` Florian Fainelli
2026-10-14 21:48 ` Pavel Machek
2026-10-15 5:05 ` Ron Economos
2026-10-15 6:16 ` Miguel Ojeda
[not found] ` <6d8a0529-033b-4d81-a2e8-cf735e9a4b7b@rnnvmail204.nvidia.com>
2026-10-15 13:16 ` Jon Hunter [this message]
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=2a5adbe8-ed67-476b-bffd-169c8c50f686@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=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@nabladev.com \
--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
all inboxes | Powered by JetHome®