Set unevaluatedProperties:false in ak4458 dt-binding doc.
Fix supply name in ak4458 and ak5558 dt-binding doc.

Changes in v2:
- update the commit message for patch 1/3.
- Fix the supply name in dt-binding doc, not in driver, replace the
  patch 2/3 and 3/3.

Shengjiu Wang (3):
  ASoC: dt-bindings: asahi-kasei,ak4458: set unevaluatedProperties:false
  ASoC: dt-bindings: asahi-kasei,ak4458: Fix the supply names
  ASoC: dt-bindings: asahi-kasei,ak5558: Fix the supply names

 .../devicetree/bindings/sound/asahi-kasei,ak4458.yaml       | 6 +++---
 .../devicetree/bindings/sound/asahi-kasei,ak5558.yaml       | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

-- 
2.34.1

On Thu, 12 Feb 2026 10:18:26 +0800, Shengjiu Wang wrote:
> Set unevaluatedProperties:false in ak4458 dt-binding doc.
> Fix supply name in ak4458 and ak5558 dt-binding doc.
> 
> Changes in v2:
> - update the commit message for patch 1/3.
> - Fix the supply name in dt-binding doc, not in driver, replace the
>   patch 2/3 and 3/3.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: dt-bindings: asahi-kasei,ak4458: set unevaluatedProperties:false
      commit: 50a634f1d795721ce68583c78ba493f1d7aa8bc2
[2/3] ASoC: dt-bindings: asahi-kasei,ak4458: Fix the supply names
      commit: e570a5ca307f6d7a6acd080fc219db2ce3c0737b
[3/3] ASoC: dt-bindings: asahi-kasei,ak5558: Fix the supply names
      commit: 80ca113671a005430207d351cb403c1637106212

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