[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c8e268b3-2d7e-79d7-fee2-03cbd698636a@roeck-us.net>
Date: Mon, 19 Sep 2022 05:43:18 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Pavel Machek <pavel@...x.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
slade@...dewatkins.com
Subject: Re: 5.10.144 got more patches? was Re: [PATCH 5.10 00/24]
5.10.144-rc1 review
On 9/19/22 03:33, Pavel Machek wrote:
> Hi!
>
>>> This is the start of the stable review cycle for the 5.10.144 release.
>>> There are 24 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.
>>
>> CIP testing did not find any problems here:
>>
>> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.10.y
>>
>> Tested-by: Pavel Machek (CIP) <pavel@...x.de>
>
> And now I'm confused.
>
> 5.10.144-rc1 was announced / tested, but now there's buch more patches
> in the queue, starting with
>
> |9843b839a 174974 .: 5.10| drm/msm/rd: Fix FIFO-full deadlock
> |518b67da4 174974 .: 4.19| drm/msm/rd: Fix FIFO-full deadlock
> |88eba3686 174974 .: 4.9| drm/msm/rd: Fix FIFO-full deadlock
>
I don't see added commits, but one commit was dropped after the author
complained that it should not be applied to stable releases.
Guenter
Powered by blists - more mailing lists