Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Alexey Makhalov <alexey.makhalov@broadcom.com>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	virtualization@lists.linux.dev, x86@kernel.org
Cc: gregkh@linuxfoundation.org, bp@alien8.de,
	ajay.kaher@broadcom.com,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] MAINTAINERS: update Alexey Makhalov's email address
Date: Wed, 30 Apr 2025 15:03:15 -0700	[thread overview]
Message-ID: <2fe44a46-cd13-47a8-8873-56292028b165@broadcom.com> (raw)
In-Reply-To: <20250318004031.2703923-1-alexey.makhalov@broadcom.com>

Hi Borislav,

I see this patch didn't get a traction.
Can you to merge this fix in x86 tree, please?

Thanks,
--Alexey

On 3/17/25 5:40 PM, Alexey Makhalov wrote:
> Fix a typo in an email address.
> 
> Cc: stable@vger.kernel.org
> Reported-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> Closes: https://lore.kernel.org/all/20240925-rational-succinct-vulture-cca9fb@lemur/T/
> Signed-off-by: Alexey Makhalov <alexey.makhalov@broadcom.com>
> ---
>   MAINTAINERS | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c9763412a508..c2eb78c1ab75 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17945,7 +17945,7 @@ F:	include/uapi/linux/ppdev.h
>   PARAVIRT_OPS INTERFACE
>   M:	Juergen Gross <jgross@suse.com>
>   R:	Ajay Kaher <ajay.kaher@broadcom.com>
> -R:	Alexey Makhalov <alexey.amakhalov@broadcom.com>
> +R:	Alexey Makhalov <alexey.makhalov@broadcom.com>
>   R:	Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
>   L:	virtualization@lists.linux.dev
>   L:	x86@kernel.org
> @@ -25341,7 +25341,7 @@ F:	drivers/misc/vmw_balloon.c
>   
>   VMWARE HYPERVISOR INTERFACE
>   M:	Ajay Kaher <ajay.kaher@broadcom.com>
> -M:	Alexey Makhalov <alexey.amakhalov@broadcom.com>
> +M:	Alexey Makhalov <alexey.makhalov@broadcom.com>
>   R:	Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
>   L:	virtualization@lists.linux.dev
>   L:	x86@kernel.org
> @@ -25369,7 +25369,7 @@ F:	drivers/scsi/vmw_pvscsi.h
>   VMWARE VIRTUAL PTP CLOCK DRIVER
>   M:	Nick Shi <nick.shi@broadcom.com>
>   R:	Ajay Kaher <ajay.kaher@broadcom.com>
> -R:	Alexey Makhalov <alexey.amakhalov@broadcom.com>
> +R:	Alexey Makhalov <alexey.makhalov@broadcom.com>
>   R:	Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
>   L:	netdev@vger.kernel.org
>   S:	Supported


  reply	other threads:[~2025-04-30 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  0:40 [PATCH] MAINTAINERS: update Alexey Makhalov's email address Alexey Makhalov
2025-04-30 22:03 ` Alexey Makhalov [this message]
2025-05-12 11:45 ` [tip: x86/urgent] MAINTAINERS: Update " tip-bot2 for Alexey Makhalov
     [not found] <20240926174337.1139107-1-alexey.makhalov@broadcom.com>
2024-11-12 23:50 ` [PATCH] MAINTAINERS: update " Alexey Makhalov
2024-11-12 23:52   ` kernel test robot

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=2fe44a46-cd13-47a8-8873-56292028b165@broadcom.com \
    --to=alexey.makhalov@broadcom.com \
    --cc=ajay.kaher@broadcom.com \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=virtualization@lists.linux.dev \
    --cc=x86@kernel.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