DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jochen Behrens <jochen.behrens@broadcom.com>
To: "Ferruh Yigit" <ferruh.yigit@amd.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] maintainers: change e-mail for vmxnet3
Date: Mon, 15 Apr 2024 17:50:40 -0700	[thread overview]
Message-ID: <1e781c29-54a5-419a-b899-7b28cb99129f@broadcom.com> (raw)
In-Reply-To: <5e74fb66-f862-4960-8bb6-1142388c739f@amd.com>


I submitted a separate patch cleaning up all vmware addresses in .mailmap.

Thanks for pointing this out,

	Jochen


On 4/8/24 1:58 AM, Ferruh Yigit wrote:
> On 4/6/2024 10:03 AM, Morten Brørup wrote:
>>> From: Jochen Behrens [mailto:jochen.behrens@broadcom.com]
>>> Sent: Friday, 5 April 2024 23.56
>>>
>>> Change my address as VMware was acquired by Broadcom.
>>>
>>> Signed-off-by: Jochen Behrens <jochen.behrens@broadcom.com>
>>> ---
>>>   MAINTAINERS | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 7abb3aee49..7b13e2b036 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -981,7 +981,7 @@ F: doc/guides/nics/txgbe.rst
>>>   F: doc/guides/nics/features/txgbe.ini
>>>
>>>   VMware vmxnet3
>>> -M: Jochen Behrens <jbehrens@vmware.com>
>>> +M: Jochen Behrens <jochen.behrens@broadcom.com>
>>>   F: drivers/net/vmxnet3/
>>>   F: doc/guides/nics/vmxnet3.rst
>>>   F: doc/guides/nics/features/vmxnet3.ini
>>> --
>>
>> You might want to update .mailmap too.
>>
> 
> +1
> 
> Probably this needs to be done for all @vmware.com domain emails.
> @Jochen, would you mind spreading the word to the relevant people in
> that list?
> 
> Perhaps all changes can be done in one go, for this we need to know
> which accounts are still active, and I guess you can find this out
> internally.

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

  reply	other threads:[~2024-04-16  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 21:56 Jochen Behrens
2024-04-06  9:03 ` Morten Brørup
2024-04-08  8:58   ` Ferruh Yigit
2024-04-16  0:50     ` Jochen Behrens [this message]
2024-06-19  6:19       ` Thomas Monjalon

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=1e781c29-54a5-419a-b899-7b28cb99129f@broadcom.com \
    --to=jochen.behrens@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=mb@smartsharesystems.com \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).