mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 alsa-devel@alsa-project.org, srini@kernel.org
Subject: Re: [PATCH 0/2] MAINTAINERS: update my email address
Date: Fri, 11 Apr 2025 07:21:39 +0100	[thread overview]
Message-ID: <174435249981.1315708.17163326951823552256.b4-ty@kernel.org> (raw)
In-Reply-To: <20250410103713.24875-1-srinivas.kandagatla@linaro.org>

On Thu, 10 Apr 2025 11:37:11 +0100, srinivas.kandagatla@linaro.org wrote:
> Update .mailmap and MAINTAINERS to point to the @kernel.org instead of
> the @linaro.org. Linaro address will stop working in few days.
> 
> Mark or Greg, could you please pick these two patches?
> 
> Srinivas Kandagatla (2):
>   MAINTAINERS: use kernel.org alias
>   mailmap: Add entry for Srinivas Kandagatla
> 
> [...]

Applied to

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

Thanks!

[1/2] MAINTAINERS: use kernel.org alias
      commit: 7f33f247138554b84729688169dfbe87724b70ef
[2/2] mailmap: Add entry for Srinivas Kandagatla
      commit: 807c1c83152138e2fc22101a57b9346159ad4f4c

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:[~2025-04-11  6:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 10:37 srinivas.kandagatla
2025-04-10 10:37 ` [PATCH 1/2] MAINTAINERS: use kernel.org alias srinivas.kandagatla
2025-04-10 10:37 ` [PATCH 2/2] mailmap: Add entry for Srinivas Kandagatla srinivas.kandagatla
2025-04-11  6:21 ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-05 22:44 [PATCH 0/2] MAINTAINERS: update my email address Dmitry Baryshkov

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=174435249981.1315708.17163326951823552256.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srini@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    /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®