[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <168547572955.1446927.6113726229906083649.b4-ty@kernel.org>
Date: Tue, 30 May 2023 20:42:09 +0100
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Heiko Stuebner <heiko@...ech.de>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Zhu Ning <zhuning0077@...il.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
David Yang <yangxiaohua@...rest-semi.com>,
Daniel Drake <drake@...lessm.com>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
alsa-devel@...a-project.org, kernel@...labora.com
Subject: Re: (subset) [PATCH v2 0/3] ES8316 audio codec fixes on Rock5B
On Tue, 30 May 2023 21:11:37 +0300, Cristian Ciocaltea wrote:
> This patch series handles a few issues related to the ES8316 audio
> codec, discovered while doing some testing on the Rock 5B board.
>
> Changes in v2:
> - Preserved original dB gain range in PATCH 1
> - Rewrote PATCH 2 conditional statement, per Mark's review
> - Rebased series onto next-20230530
> - v1: https://lore.kernel.org/all/20230524074156.147387-1-cristian.ciocaltea@collabora.com/
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: es8316: Increment max value for ALC Capture Target Volume control
commit: 6f073429037cd79d7311cd8236311c53f5ea8f01
[2/3] ASoC: es8316: Do not set rate constraints for unsupported MCLKs
commit: 60413129ee2b38a80347489270af7f6e1c1de4d0
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
Powered by blists - more mailing lists