mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	 Daniel Baluta <daniel.baluta@nxp.com>,
	 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	 Liam Girdwood <lgirdwood@gmail.com>,
	linux-sound@vger.kernel.org,  Lukas Bulwahn <lbulwahn@redhat.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: adjust file entries after adding vendor prefix in sound dtbs
Date: Tue, 25 Jun 2024 19:12:19 +0100	[thread overview]
Message-ID: <171933913995.1078071.14226785405365723718.b4-ty@kernel.org> (raw)
In-Reply-To: <20240625033419.149775-1-lukas.bulwahn@redhat.com>

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


      parent reply	other threads:[~2024-06-25 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25  3:34 Lukas Bulwahn
2024-06-25  3:55 ` Kuninori Morimoto
2024-06-25 18:12 ` 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=171933913995.1078071.14226785405365723718.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lbulwahn@redhat.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=lukas.bulwahn@redhat.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®