From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.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,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 6.5 000/321] 6.5.6-rc1 review
Date: Fri, 6 Oct 2023 10:40:29 +0100 [thread overview]
Message-ID: <018d458a-2d99-40ae-b8e7-e832b44a6478@nvidia.com> (raw)
In-Reply-To: <20231004175229.211487444@linuxfoundation.org>
On 04/10/2023 18:52, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.5.6 release.
> There are 321 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, 06 Oct 2023 17:51:12 +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.5.6-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.5.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
We have one test failure for Tegra, but this is expected at the moment [0].
Test results for stable-v6.5:
10 builds: 10 pass, 0 fail
26 boots: 26 pass, 0 fail
116 tests: 115 pass, 1 fail
Linux version: 6.5.6-rc1-g9327d0db36be
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: tegra-audio-dmic-capture.sh
The fixes are now in the mainline, so would be good to pull these when
possible.
e765886249c5 ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates
f101583fa9f8 ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol
Otherwise ...
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Thanks
Jon
[0]
https://lore.kernel.org/lkml/dfe78c1a-8322-413b-f1b7-3a6a307a831c@nvidia.com/
--
nvpublic
next prev parent reply other threads:[~2023-10-06 9:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 17:52 Greg Kroah-Hartman
2023-10-04 19:54 ` Florian Fainelli
2023-10-05 0:54 ` Shuah Khan
2023-10-05 1:33 ` SeongJae Park
2023-10-05 4:04 ` Bagas Sanjaya
2023-10-05 5:35 ` Naresh Kamboju
2023-10-05 14:55 ` Naresh Kamboju
2023-10-06 9:54 ` Greg Kroah-Hartman
2023-10-05 5:55 ` Naresh Kamboju
2023-10-05 14:34 ` Jakub Kicinski
[not found] ` <be48ca60-57dd-9bbb-d695-0d9d39e98dae@w6rz.net>
2023-10-05 16:28 ` Florian Fainelli
2023-10-05 16:36 ` Justin Forbes
2023-10-05 22:16 ` Guenter Roeck
2023-10-06 9:40 ` Jon Hunter [this message]
2023-10-04 18:44 Ronald Warsow
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=018d458a-2d99-40ae-b8e7-e832b44a6478@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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
Powered by JetHome