linux-kernel - Re: [PATCH] MAINTAINERS: refer to trivial-codec.yaml in relevant sections

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

Message-Id: <176313773331.173018.5617582229167638951.b4-ty@kernel.org>
Date: Fri, 14 Nov 2025 16:28:53 +0000
From: Mark Brown <broonie@...nel.org>
To: Frank Li <Frank.Li@....com>, Lars-Peter Clausen <lars@...afoo.de>, 
 Nuno Sá <nuno.sa@...log.com>, 
 Liam Girdwood <lgirdwood@...il.com>, 
 Martin Povišer <povik+lin@...ebit.org>, 
 Support Opensource <support.opensource@...semi.com>, 
 Peter Rosin <peda@...ntia.se>, linux-sound@...r.kernel.org, 
 devicetree@...r.kernel.org, asahi@...ts.linux.dev, 
 patches@...nsource.cirrus.com, Lukas Bulwahn <lbulwahn@...hat.com>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Lukas Bulwahn <lukas.bulwahn@...hat.com>
Subject: Re: [PATCH] MAINTAINERS: refer to trivial-codec.yaml in relevant
 sections

On Fri, 14 Nov 2025 12:37:12 +0100, Lukas Bulwahn wrote:
> Commit 4acbfcf11cbe ("ASoC: dt-bindings: consolidate simple audio codec to
> trivial-codec.yaml") aggregates a few sound device-tree bindings, i.e., txt
> and yaml files, into a common trivial-codec.yaml, but misses to adjust the
> references in ANALOG DEVICES INC ASOC CODEC DRIVERS, ARM/APPLE MACHINE
> SOUND DRIVERS, NXP TFA9879 DRIVER and WOLFSON MICROELECTRONICS DRIVERS,
> which refer to files removed by the commit above.
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: refer to trivial-codec.yaml in relevant sections
      commit: 6402ddf3027d8975f135cf2b2014d6bbeb2d3436

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