From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Jack Yu <jack.yu@realtek.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
alsa-devel@alsa-project.org, lars@metafoo.de,
derek.fang@realtek.com, shumingf@realtek.com,
"Flove\(HsinFu\)" <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt715-sdca: fix clock stop prepare timeout issue
Date: Mon, 30 Jan 2023 19:33:33 +0000 [thread overview]
Message-ID: <167510721304.1539540.12025220772981094616.b4-ty@kernel.org> (raw)
In-Reply-To: <574b6586267a458cac78c5ac4d5b10bd@realtek.com>
On Mon, 30 Jan 2023 02:43:25 +0000, Jack Yu wrote:
> Modify clock_stop_timeout value for rt715-sdca according to
> the requirement of internal clock trimming.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: rt715-sdca: fix clock stop prepare timeout issue
commit: 2036890282d56bcbf7f915ba9e04bf77967ab231
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:[~2023-01-30 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 2:43 [PATCH] ASoC: rt715-sdca: fix clock stop prepare timeout issue Jack Yu
2023-01-30 19:33 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-21 7:01 Jack Yu
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=167510721304.1539540.12025220772981094616.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=shumingf@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.