On 9/18/23 05:56, Greg Kroah-Hartman wrote:
On Mon, Sep 18, 2023 at 01:52:10PM +0100, Jon Hunter wrote:
Hi Greg,
On 17/09/2023 20:10, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.5.4 release.
There are 285 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, 19 Sep 2023 19:10:04 +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.4-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
-------------
Pseudo-Shortlog of commits:
...
Sameer Pujar <spujar@xxxxxxxxxx>
arm64: tegra: Update AHUB clock parent and rate
Unfortunately, the above change is causing a regression in one of our audio
tests and we are looking into why this is.
Can we drop this from stable for now?
Is it also a problem in Linus's tree? Keeping bug-compatible is always
good :)
Sorry, no, it isn't, especially in the context of at the same time suggesting
that everyone should start using the most recent stable release immediately
(instead of, say, selectively picking security patches).
I don't think Tegra users would be happy if their audio stopped working,
and it seems unlikely that they would accept the argument that they should
be happy to be bug-compatible with the latest upstream kernel - even more so
if that latest upstream kernel is a release candidate and the problem was
introduced in the commit window.
Guenter
