[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172778121572.2280749.3048462139330835631.b4-ty@kernel.org>
Date: Tue, 01 Oct 2024 12:13:35 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
linux-sound@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Alexandre Mergnat <amergnat@...libre.com>,
Macpaul Lin <macpaul.lin@...iatek.com>
Cc: Bear Wang <bear.wang@...iatek.com>, Pablo Sun <pablo.sun@...iatek.com>,
Macpaul Lin <macpaul@...il.com>, Sen Chu <sen.chu@...iatek.com>,
Chris-qj chen <chris-qj.chen@...iatek.com>,
MediaTek Chromebook Upstream <Project_Global_Chrome_Upstream_Group@...iatek.com>,
Chen-Yu Tsai <wenst@...omium.org>, Jiaxin Yu <jiaxin.yu@...iatek.com>
Subject: Re: (subset) [PATCH v2 1/2] ASoC: dt-bindings: mt6359: Update
generic node name and dmic-mode
On Mon, 30 Sep 2024 15:54:50 +0800, Macpaul Lin wrote:
> Some fix and updates in the following items:
> 1. examples:
> Update generic node name to 'audio-codec' to comply with the
> coming change in 'mt6359.dtsi'. This change is necessary to fix the
> dtbs_check error:
> pmic: 'mt6359codec' does not match any of the regexes: 'pinctrl-[0-9]+'
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: dt-bindings: mt6359: Update generic node name and dmic-mode
commit: 4649cbd97fdae5069e9a71cd7669b62b90e03669
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