From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
Sameer Pujar <spujar@nvidia.com>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Fix redundant PLLA update
Date: Tue, 12 Sep 2023 01:01:50 +0100 [thread overview]
Message-ID: <169447691068.2390116.10518505217580469969.b4-ty@kernel.org> (raw)
In-Reply-To: <1694098945-32760-1-git-send-email-spujar@nvidia.com>
On Thu, 07 Sep 2023 20:32:23 +0530, Sameer Pujar wrote:
> This small series fixes redundant PLLA updates that happen for
> each DAI link in the audio path. This helps to resolve DMIC clock
> issue seen on Jetson TX2 platform.
>
> Sameer Pujar (2):
> ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol
> ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol
commit: f101583fa9f8c3f372d4feb61d67da0ccbf4d9a5
[2/2] ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates
commit: e765886249c533e1bb5cbc3cd741bad677417312
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2023-09-12 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 15:02 Sameer Pujar
2023-09-07 15:02 ` [PATCH v2 1/2] ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol Sameer Pujar
2023-09-07 15:02 ` [PATCH v2 2/2] ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates Sameer Pujar
2023-09-12 0:01 ` Mark Brown [this message]
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=169447691068.2390116.10518505217580469969.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®