From: Mark Brown <broonie@kernel.org>
To: Ravulapati Vishnu vardhan rao <Vishnuvardhanrao.Ravulapati@amd.com>
Cc: YueHaibing <yuehaibing@huawei.com>,
Akshu Agrawal <akshu.agrawal@amd.com>,
Takashi Iwai <tiwai@suse.com>,
open list <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
"moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH] ASoC: amd: Replacing component->name with codec_dai->name.
Date: Mon, 10 Aug 2020 19:57:37 +0100 [thread overview]
Message-ID: <159708585778.21544.6105226494365103572.b4-ty@kernel.org> (raw)
In-Reply-To: <20200807161046.17932-1-Vishnuvardhanrao.Ravulapati@amd.com>
On Fri, 7 Aug 2020 21:40:17 +0530, Ravulapati Vishnu vardhan rao wrote:
> Replacing string compare with "codec_dai->name" instead of comparing with
> "codec_dai->component->name" in hw_params because,
> Here the component name for codec RT1015 is "i2c-10EC5682:00"
> and will never be "rt1015-aif1" as it is codec-dai->name.
> So, strcmp() always compares and fails to set the
> sysclk,pll,bratio for expected codec-dai="rt1015-aif1".
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: amd: Replacing component->name with codec_dai->name.
commit: ea7dc097826b06a9746a2e74c2d6e78d35c98088
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
next prev parent reply other threads:[~2020-08-10 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 16:10 [PATCH] ASoC: amd: Replacing component->name with codec_dai->name Ravulapati Vishnu vardhan rao
2020-08-10 18:57 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-06 10:14 Ravulapati Vishnu vardhan rao
2020-08-06 11:28 ` Mark Brown
2020-08-07 8:09 ` RAVULAPATI, VISHNU VARDHAN RAO
2020-08-07 8:36 ` RAVULAPATI, VISHNU VARDHAN RAO
2020-08-07 11:54 ` Mark Brown
2020-08-10 18:57 ` Mark Brown
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=159708585778.21544.6105226494365103572.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Vishnuvardhanrao.Ravulapati@amd.com \
--cc=akshu.agrawal@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=yuehaibing@huawei.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).