linux-kernel - Re: [PATCH] MAINTAINERS: update Qualcomm audio codec drivers list

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <175128362404.28563.7607369612683502987.b4-ty@kernel.org>
Date: Mon, 30 Jun 2025 12:40:24 +0100
From: Mark Brown <broonie@...nel.org>
To: srinivas.kandagatla@....qualcomm.com
Cc: linux-kernel@...r.kernel.org, linux-sound@...r.kernel.org, 
 linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update Qualcomm audio codec drivers list

On Fri, 27 Jun 2025 17:03:29 +0100, srinivas.kandagatla@....qualcomm.com wrote:
> Some of the codec drivers like wcd939x are missing in the MAINTAINERS
> which is resulting in incorrect list from get_maintainers script.
> Fix this by using wildcard matching on both wcd93* and wsa88* codec and
> bindings.
> 
> 

Applied to

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

Thanks!

[1/1] MAINTAINERS: update Qualcomm audio codec drivers list
      commit: be2e1a63448b35bd6736b5934f7720534649b51e

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