linux-kernel - Re: [v2 0/2] ASoC: mediatek: mt8186_mt6366_rt1019

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <169774846545.93224.1171196773910297821.b4-ty@kernel.org>
Date:   Thu, 19 Oct 2023 21:47:45 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, robh+dt@...nel.org,
        angelogioacchino.delregno@...labora.com, matthias.bgg@...il.com,
        perex@...ex.cz, trevor.wu@...iatek.com, jiaxin.yu@...iatek.com,
        xiazhengqiao <xiazhengqiao@...qin.corp-partner.google.com>
Cc:     alsa-devel@...a-project.org, devicetree@...r.kernel.org,
        linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [v2 0/2] ASoC: mediatek: mt8186_mt6366_rt1019_rt5682s: add
 rt5650 support

On Thu, 19 Oct 2023 18:03:20 +0800, xiazhengqiao wrote:
> To use RT5650 as the codec and the amp, add a new
> sound card named mt8186_rt5650.
> 
> Changes in v2:
> - PATCH 2/2: Modify the code format in line 1058
> - Link to v1: https://lore.kernel.org/all/54ec6435-e69b-444a-a31a-c878a4b3564a@collabora.com/
>               https://lore.kernel.org/all/8de0772b-3145-44e3-8174-702c7dc729bb@collabora.com/
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: dt-bindings: mt8186-mt6366-rt1019-rt5682s: add RT5650 support
      commit: 8a79ff9e46beee03dfc2ce9cc80f7090f57d64cb
[2/2] ASoC: mediatek: mt8186_mt6366_rt1019_rt5682s: add rt5650 support
      commit: d88c433831015a4ad4597885cef8f048808cd94d

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