linux-kernel - Re: [PATCH] ASoC: Add Cirrus and Wolfson headers to ASoC section of MAINTAINERS

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: <174475380680.1274591.1263818391223217277.b4-ty@kernel.org>
Date: Tue, 15 Apr 2025 22:50:06 +0100
From: Mark Brown <broonie@...nel.org>
To: tiwai@...e.com, Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: Add Cirrus and Wolfson headers to ASoC section
 of MAINTAINERS

On Tue, 15 Apr 2025 13:29:27 +0100, Richard Fitzgerald wrote:
> Specifically list various Cirrus Logic and Wolfson Micro codec header files
> under include/sound/ within the ASoC section of MAINTAINERS. Note that not
> all the include/sound/cs* files are part of ASoC, so more-specific patterns
> are needed.
> 
> These files are all part of ASoC codec drivers, and are owned by specific
> Cirrus Logic and Wolfson Micro sections of MAINTAINERS. But the overall
> include/sound/* maintainership is only Takashi Iwai and Jaroslav Kysela.
> So by default get_maintainer.pl would only show Takashi and Jaroslav as
> maintainers for any patch that changes these files without changing any
> code under sound/soc.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Add Cirrus and Wolfson headers to ASoC section of MAINTAINERS
      commit: 63ec4baf725cbde506f0a9640ae6751622b81b0a

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