mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
	 support.opensource@diasemi.com,
	Liam Girdwood <lgirdwood@gmail.com>,
	 Lukas Bulwahn <lbulwahn@redhat.com>
Cc: Rob Herring <robh@kernel.org>,
	 AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	 kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: remove obsolete file entry in DIALOG SEMICONDUCTOR DRIVERS
Date: Thu, 30 Oct 2025 11:09:25 +0000	[thread overview]
Message-ID: <176182256554.10414.9428685076956872040.b4-ty@kernel.org> (raw)
In-Reply-To: <20251029081516.83298-1-lukas.bulwahn@redhat.com>

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


      reply	other threads:[~2025-10-30 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29  8:15 Lukas Bulwahn
2025-10-30 11:09 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=176182256554.10414.9428685076956872040.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=ariel.dalessandro@collabora.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lbulwahn@redhat.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=robh@kernel.org \
    --cc=support.opensource@diasemi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®