linux-kernel - Re: [PATCH] MAINTAINERS: remove obsolete file entry in DIALOG SEMICONDUCTOR DRIVERS

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: <176182256554.10414.9428685076956872040.b4-ty@kernel.org>
Date: Thu, 30 Oct 2025 11:09:25 +0000
From: Mark Brown <broonie@...nel.org>
To: Ariel D'Alessandro <ariel.dalessandro@...labora.com>, 
 support.opensource@...semi.com, Liam Girdwood <lgirdwood@...il.com>, 
 Lukas Bulwahn <lbulwahn@...hat.com>
Cc: Rob Herring <robh@...nel.org>, 
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, 
 kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Lukas Bulwahn <lukas.bulwahn@...hat.com>
Subject: Re: [PATCH] MAINTAINERS: remove obsolete file entry in DIALOG
 SEMICONDUCTOR DRIVERS

On Wed, 29 Oct 2025 09:15:16 +0100, Lukas Bulwahn wrote:
> Commit 6277a486a7fa ("regulator: dt-bindings: Convert Dialog DA9211
> Regulators to DT schema") converts the last txt dt-binding in DIALOG
> SEMICONDUCTOR DRIVERS to the yaml format. With that, there is no file,
> which matches the pattern for the dt-binding txt file entry in that
> section. The existing yaml files are already covered by the file entry with
> the pattern dlg,da9*.yaml.
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: remove obsolete file entry in DIALOG SEMICONDUCTOR DRIVERS
      commit: 28039efa4d8e8bbf98b066133a906bd4e307d496

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