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,
allen.lkml@gmail.com, linux-tegra@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 5.10 000/187] 5.10.202-rc3 review
Date: Mon, 27 Nov 2023 23:37:17 +0000 [thread overview]
Message-ID: <6e45696d-fe6b-4570-8ca7-481de78a983f@nvidia.com> (raw)
In-Reply-To: <fc421b26-ed60-48fa-a2f4-0fafcb44e91c@drhqmail201.nvidia.com>
On 27/11/2023 23:27, Jon Hunter wrote:
> On Sun, 26 Nov 2023 15:46:55 +0000, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 5.10.202 release.
>> There are 187 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 Tue, 28 Nov 2023 15:43:06 +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.202-rc3.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
> 26 boots: 26 pass, 0 fail
> 68 tests: 67 pass, 1 fail
>
> Linux version: 5.10.202-rc3-g80dc4301c91e
> 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: tegra194-p2972-0000: boot.py
After commit the commit "gpio: Don't fiddle with irqchips marked as
immutable" added, we observe the following warnings and is causing a
test to fail ...
WARNING KERN gpio gpiochip0: (max77620-gpio): not an immutable chip,
please consider fixing it!
WARNING KERN gpio gpiochip1: (tegra194-gpio): not an immutable chip,
please consider fixing it!
WARNING KERN gpio gpiochip2: (tegra194-gpio-aon): not an immutable
chip, please consider fixing it!
The following upstream changes fix these ...
7d1aa08aff06 gpio: tegra: Convert to immutable irq chip
bba00555ede7 gpio: tegra186: Make the irqchip immutable
7f42aa7b008c gpio: max77620: Make the irqchip immutable
There are quite a few other drivers that were updated in a similar way,
so the above only fix the ones we observe on Tegra.
Jon
--
nvpublic
next prev parent reply other threads:[~2023-11-27 23:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 15:46 [PATCH 5.10 000/187] 5.10.202-rc3 review Greg Kroah-Hartman
2023-11-26 16:22 ` Guenter Roeck
2023-11-27 11:45 ` [PATCH 5.10] interconnect: qcom: Add support for mask-based BCMs djakov
2023-11-27 12:40 ` Greg KH
2023-11-26 18:23 ` [PATCH 5.10 000/187] 5.10.202-rc3 review Guenter Roeck
2023-11-27 12:40 ` Greg Kroah-Hartman
2023-11-27 3:51 ` Florian Fainelli
2023-11-27 21:25 ` Pavel Machek
2023-11-28 6:56 ` Dominique Martinet
2023-11-28 20:43 ` Pavel Machek
2023-11-28 10:42 ` Richard Fitzgerald
2023-11-28 20:40 ` Pavel Machek
2023-11-29 11:35 ` Richard Fitzgerald
2023-11-27 23:27 ` Jon Hunter
2023-11-27 23:37 ` Jon Hunter [this message]
2023-11-28 9:42 ` Greg Kroah-Hartman
2023-11-28 2:52 ` Guenter Roeck
2023-11-28 9:30 ` Naresh Kamboju
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=6e45696d-fe6b-4570-8ca7-481de78a983f@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--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