From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, 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,
Sameer Pujar <spujar@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 6.5 000/285] 6.5.4-rc1 review
Date: Mon, 18 Sep 2023 15:44:48 +0100 [thread overview]
Message-ID: <5241ef7b-dfa3-625c-0aa0-4af10a1c1a52@nvidia.com> (raw)
In-Reply-To: <2023091850-gossip-denatured-ce2b@gregkh>
On 18/09/2023 14:14, Greg Kroah-Hartman wrote:
> On Mon, Sep 18, 2023 at 02:04:27PM +0100, Jon Hunter wrote:
>>
>> On 18/09/2023 13:52, 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@nvidia.com>
>>>> 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?
>>
>>
>> An alternative to dropping this change is to pull in the following fixes ...
>>
>> https://lore.kernel.org/linux-tegra/169447691068.2390116.10518505217580469969.b4-ty@kernel.org/T/#t
>
> they aren't in Linus's tree yet, any plans on when that will happen?
Not clear at the moment, I see Mark has them queued up here ...
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/log/?h=for-6.6
> And to confirm, what are the git ids of these in linux-next?
In next I see the following git ids ...
e765886249c5 ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates
f101583fa9f8 ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2023-09-18 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230917191051.639202302@linuxfoundation.org>
2023-09-18 12:52 ` [PATCH 6.5 000/285] 6.5.4-rc1 review Jon Hunter
2023-09-18 12:56 ` Greg Kroah-Hartman
2023-09-18 14:31 ` Jon Hunter
2023-09-18 15:17 ` Guenter Roeck
2023-09-19 7:55 ` Greg Kroah-Hartman
2023-09-18 19:47 ` Pavel Machek
2023-09-18 13:04 ` Jon Hunter
2023-09-18 13:14 ` Greg Kroah-Hartman
2023-09-18 14:44 ` Jon Hunter [this message]
2023-09-19 7:54 ` Greg Kroah-Hartman
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=5241ef7b-dfa3-625c-0aa0-4af10a1c1a52@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=spujar@nvidia.com \
--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