linux-kernel - Re: [PATCH] MAINTAINERS: adjust file entries after adding vendor prefix in sound dtbs

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: <171933913995.1078071.14226785405365723718.b4-ty@kernel.org>
Date: Tue, 25 Jun 2024 19:12:19 +0100
From: Mark Brown <broonie@...nel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
 Daniel Baluta <daniel.baluta@....com>, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 
 Liam Girdwood <lgirdwood@...il.com>, linux-sound@...r.kernel.org, 
 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: adjust file entries after adding vendor
 prefix in sound dtbs

On Tue, 25 Jun 2024 05:34:19 +0200, Lukas Bulwahn wrote:
> Commit ae8fc2948b48 ("ASoC: dt-bindings: add missing vender prefix on
> filename") renames a few files in Documentation/devicetree/bindings/sound/,
> but misses to adjust the file entries pointing to those files in
> MAINTAINERS.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about
> broken references.
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: adjust file entries after adding vendor prefix in sound dtbs
      commit: 15c99e7fa9e2bb536e813478250d2a609863dcfb

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