[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165835873701.1007579.13802197177165168890.b4-ty@kernel.org>
Date: Thu, 21 Jul 2022 00:12:17 +0100
From: Mark Brown <broonie@...nel.org>
To: jiaxin.yu@...iatek.com, angelogioacchino.delregno@...labora.com,
robh+dt@...nel.org
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
tzungbi@...gle.com, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org, julianbraha@...il.com,
trevor.wu@...iatek.com, linux-mediatek@...ts.infradead.org,
matthias.bgg@...il.com, aaronyu@...gle.com,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH v10 0/8] ASoC: mediatek: Add support for MT8186 SoC
On Tue, 19 Jul 2022 00:21:56 +0800, Jiaxin Yu wrote:
> This series of patches adds support for Mediatek AFE of MT8186 Soc.
> Patches are based on broonie tree "for-next" branch.
>
> Changes since v9:
> - Drop the definitions that unused in mt8186-afe-common.h.
> - Use device_get_match_data() instead of of_device_get_match_data().
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/8] dt-bindings: mediatek: mt6358: add new compatible for using mt6366
commit: 8f57d8b149b1e46b4ffa707634fe76532ec89e83
[2/8] ASoC: mediatek: mt8186: add platform driver
commit: 097e874ad3fc69601e2b142ff3b638893c355b41
[3/8] ASoC: mediatek: mt8186: add mt8186-mt6366 common driver
commit: a809ded89d1d982ac05d8a3c6c943b49ff1b94fa
[4/8] dt-bindings: mediatek: mt8186: add audio afe document
commit: 344afef6b980be569f4e9325778ca6869fed82cd
[5/8] ASoC: mediatek: mt8186: add machine driver with mt6366, da7219 and max98357
commit: 3c6e24b65b53ce22c30492b9f239853b01d2d5b2
[6/8] dt-bindings: mediatek: mt8186: add mt8186-mt6366-da7219-max98357 document
commit: 8a8da1e6af18f51b719a142fde92e5db56a129a0
[7/8] ASoC: mediatek: mt8186: add machine driver with mt6366, rt1019 and rt5682s
commit: 0da16e370dd7a17b33b6fa2769ad9536389a0e12
[8/8] dt-bindings: mediatek: mt8186: add mt8186-mt6366-rt1019-rt5682s document
commit: 1bcca73ee596e46e84782514621062c0ddf9d24f
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