From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Zack Rusin <zack.rusin@broadcom.com>, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ian Forbes <ian.forbes@broadcom.com>,
Martin Krastev <martin.krastev@broadcom.com>,
Maaz Mombasawala <maaz.mombasawala@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] MAINTAINERS: Change vmware.com addresses to broadcom.com
Date: Sun, 24 Dec 2023 10:52:27 +0100 [thread overview]
Message-ID: <82e92423-d759-47b7-9034-6b0a725d5a7f@broadcom.com> (raw)
In-Reply-To: <20231224052036.603621-1-zack.rusin@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On 12/24/2023 6:20 AM, Zack Rusin wrote:
> Update the email addresses for vmwgfx and vmmouse to reflect the fact
> that VMware is now part of Broadcom.
>
> Add a .mailmap entry because the vmware.com address will start bouncing
> soon.
>
> Signed-off-by: Zack Rusin <zack.rusin@broadcom.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Ian Forbes <ian.forbes@broadcom.com>
> Cc: Martin Krastev <martin.krastev@broadcom.com>
> Cc: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
> Cc: Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
> Cc: dri-devel@lists.freedesktop.org
> Cc: linux-kernel@vger.kernel.org
Acked-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next prev parent reply other threads:[~2023-12-24 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 5:20 Zack Rusin
2023-12-24 9:52 ` Florian Fainelli [this message]
2024-04-02 23:23 [PATCH] MAINTAINERS: change " Alexey Makhalov
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=82e92423-d759-47b7-9034-6b0a725d5a7f@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ian.forbes@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maaz.mombasawala@broadcom.com \
--cc=martin.krastev@broadcom.com \
--cc=zack.rusin@broadcom.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®