From: Dmitry Osipenko <digetx@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: alsa-devel@alsa-project.org, Erik Faye-Lund <kusmabite@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>, Stable <stable@vger.kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Sowjanya Komatineni <skomatineni@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: Request to pick up couple NVIDIA Tegra ASoC patches into 5.7 kernel
Date: Thu, 13 Aug 2020 03:24:32 +0300 [thread overview]
Message-ID: <4991edb7-011d-2dc4-e684-797b6504a122@gmail.com> (raw)
In-Reply-To: <20200813000800.GM2975990@sasha-vm>
13.08.2020 03:08, Sasha Levin пишет:
> On Wed, Aug 12, 2020 at 10:14:34PM +0300, Dmitry Osipenko wrote:
>> Hello, stable-kernel maintainers!
>>
>> Could you please cherry-pick these commits into the v5.7.x kernel?
>>
>> commit 0de6db30ef79b391cedd749801a49c485d2daf4b
>> Author: Sowjanya Komatineni <skomatineni@nvidia.com>
>> Date: Mon Jan 13 23:24:17 2020 -0800
>>
>> ASoC: tegra: Use device managed resource APIs to get the clock
>>
>> commit 1e4e0bf136aa4b4aa59c1e6af19844bd6d807794
>> Author: Sowjanya Komatineni <skomatineni@nvidia.com>
>> Date: Mon Jan 13 23:24:23 2020 -0800
>>
>> ASoC: tegra: Add audio mclk parent configuration
>>
>> commit ff5d18cb04f4ecccbcf05b7f83ab6df2a0d95c16
>> Author: Sowjanya Komatineni <skomatineni@nvidia.com>
>> Date: Mon Jan 13 23:24:24 2020 -0800
>>
>> ASoC: tegra: Enable audio mclk during tegra_asoc_utils_init()
>>
>> It will fix a huge warnings splat during of kernel boot on NVIDIA Tegra
>> SoCs. For some reason these patches haven't made into 5.7 when it was
>> released and several people complained about the warnings. Thanks in
>> advance!
>
> They never made it in because they don't have a stable tag, a fixes tag,
> or do they sound like they fix a problem :)
>
> Do you have a reference to the issue at hand here?
https://lore.kernel.org/lkml/64b70163-05be-e4f9-2dbc-5088ac2a3af9@nvidia.com/
> Either way, 5.7 is alive for only about 1 or 2 weeks, is anyone still
> stuck on 5.7?
>
I didn't know that 5.7 is about to die, let's not bother with it then.
Thanks!
next prev parent reply other threads:[~2020-08-13 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 19:14 Request to pick up couple NVIDIA Tegra ASoC patches into 5.7 kernel Dmitry Osipenko
2020-08-13 0:08 ` Sasha Levin
2020-08-13 0:24 ` Dmitry Osipenko [this message]
2020-08-20 8:15 ` 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=4991edb7-011d-2dc4-e684-797b6504a122@gmail.com \
--to=digetx@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=kusmabite@gmail.com \
--cc=linux-tegra@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=skomatineni@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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