linux-kernel - Re: (subset) [PATCH v4 0/6] dt-bindings: goldfish: Convert to DT schema

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <176842660309.229619.6412457616367822654.b4-ty@kernel.org>
Date: Wed, 14 Jan 2026 21:36:43 +0000
From: Mark Brown <broonie@...nel.org>
To: airlied@...il.com, simona@...ll.ch, maarten.lankhorst@...ux.intel.com, 
 mripard@...nel.org, tzimmermann@...e.de, robh@...nel.org, 
 krzk+dt@...nel.org, conor+dt@...nel.org, dmitry.torokhov@...il.com, 
 sre@...nel.org, gregkh@...uxfoundation.org, jirislaby@...nel.org, 
 lgirdwood@...il.com, Kuan-Wei Chiu <visitorckw@...il.com>
Cc: jserv@...s.ncku.edu.tw, dri-devel@...ts.freedesktop.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-input@...r.kernel.org, linux-pm@...r.kernel.org, 
 linux-serial@...r.kernel.org, linux-sound@...r.kernel.org, 
 Yu-Chun Lin <eleanor.lin@...ltek.com>
Subject: Re: (subset) [PATCH v4 0/6] dt-bindings: goldfish: Convert to DT
 schema

On Tue, 13 Jan 2026 09:25:56 +0000, Kuan-Wei Chiu wrote:
> Convert the Android Goldfish emulator platform bindings from text
> format to DT schema.
> 
> Most of these bindings are currently located in
> Documentation/devicetree/bindings/goldfish/. Move them to the
> appropriate subsystem directories (serial, input, power, sound, misc)
> to align with the kernel directory structure.
> 
> [...]

Applied to

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

Thanks!

[5/6] dt-bindings: sound: google,goldfish-audio: Convert to DT schema
      commit: 10303b32519f52a5afd40593a507543143c8ec6a

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