From: Dmitry Osipenko <digetx@gmail.com>
To: Stable <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Sowjanya Komatineni <skomatineni@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
Erik Faye-Lund <kusmabite@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Request to pick up couple NVIDIA Tegra ASoC patches into 5.7 kernel
Date: Wed, 12 Aug 2020 22:14:34 +0300 [thread overview]
Message-ID: <2db6e1ef-5cea-d479-8a7a-8f336313cb1d@gmail.com> (raw)
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!
next reply other threads:[~2020-08-12 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 19:14 Dmitry Osipenko [this message]
2020-08-13 0:08 ` Request to pick up couple NVIDIA Tegra ASoC patches into 5.7 kernel Sasha Levin
2020-08-13 0:24 ` Dmitry Osipenko
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=2db6e1ef-5cea-d479-8a7a-8f336313cb1d@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;
as well as URLs for NNTP newsgroup(s).