[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164942922666.1424253.184773384356622992.b4-ty@kernel.org>
Date: Fri, 08 Apr 2022 15:47:06 +0100
From: Mark Brown <broonie@...nel.org>
To: tzungbi@...gle.com, robh+dt@...nel.org, jiaxin.yu@...iatek.com,
nfraprado@...labora.com
Cc: trevor.wu@...iatek.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, aaronyu@...gle.com,
matthias.bgg@...il.com, alsa-devel@...a-project.org,
linux-mediatek@...ts.infradead.org, devicetree@...r.kernel.org,
linmq006@...il.com,
Project_Global_Chrome_Upstream_Group@...iatek.com,
angelogioacchino.delregno@...labora.com
Subject: Re: [v9 0/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s
On Wed, 6 Apr 2022 18:05:10 +0800, Jiaxin Yu wrote:
> The series reuses mt8192-mt6359-rt1015-rt5682.c for supporting machine
> driver with rt1015p speaker amplifier and rt5682s headset codec.
>
> Changes from v8:
> - fix typos.
>
> Changes from v7:
> - "mediatek,hdmi-codec" is an optional property, the code and the
> binding document should match.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: dt-bindings: mt8192-mt6359: add new compatible and new properties
commit: 1efe7eca170d344c5101c69ac51df6982de764e4
[2/4] ASoC: mediatek: mt8192: refactor for I2S3 DAI link of speaker
commit: e1e408e60e856b99782b26308a9dc3937b1ba8bf
[3/4] ASoC: mediatek: mt8192: refactor for I2S8/I2S9 DAI links of headset
commit: f8910fb4985a00c0a1e6932dc5bda6181c549b76
[4/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s
commit: 7a80167b08f52e7b5eaa18a9d515efdcff9085fc
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