From: Raslan Darawsheh <rasland@nvidia.com>
To: "Minggang(Gavin) Li" <gavinl@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH V3 1/7] mailmap: update user name
Date: Thu, 31 Oct 2024 10:01:53 +0000 [thread overview]
Message-ID: <CH3PR12MB8460AADBE3D03E82C69268D9CF552@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20241029143118.875214-2-gavinl@nvidia.com>
Hi,
From: Minggang(Gavin) Li <gavinl@nvidia.com>
Sent: Tuesday, October 29, 2024 4:31 PM
To: Slava Ovsiienko; Matan Azrad; Ori Kam; NBU-Contact-Thomas Monjalon (EXTERNAL)
Cc: dev@dpdk.org; Raslan Darawsheh
Subject: [PATCH V3 1/7] mailmap: update user name
Signed-off-by: Minggang Li(Gavin) <gavinl@nvidia.com>
---
.mailmap | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.mailmap b/.mailmap
index 504c390f0f..0ce965084c 100644
--- a/.mailmap
+++ b/.mailmap
@@ -462,7 +462,6 @@ Gary Mussar <gmussar@ciena.com>
Gaurav Singh <gaurav1086@gmail.com>
Gautam Dawar <gdawar@solarflare.com>
Gavin Hu <gavin.hu@arm.com> <gavin.hu@linaro.org>
-Gavin Li <gavinl@nvidia.com>
Geoffrey Le Gourriérec <geoffrey.le_gourrierec@6wind.com>
Geoffrey Lv <geoffrey.lv@gmail.com>
Geoff Thorpe <geoff.thorpe@nxp.com>
@@ -1024,6 +1023,7 @@ Mike Ximing Chen <mike.ximing.chen@intel.com>
Milena Olech <milena.olech@intel.com>
Min Cao <min.cao@intel.com>
Minghuan Lian <minghuan.lian@nxp.com>
+Minggang Li(Gavin) <gavinl@nvidia.com>
Mingjin Ye <mingjinx.ye@intel.com>
Mingshan Zhang <mingshan.zhang@intel.com>
Mingxia Liu <mingxia.liu@intel.com>
--
2.34.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2024-10-31 10:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:38 [PATCH V1 0/7] port probe time optimization Minggang Li(Gavin)
2024-10-16 8:38 ` [PATCH V1 1/7] mailmap: update user name Minggang Li(Gavin)
2024-10-16 8:38 ` [PATCH V1 2/7] net/mlx5: optimize device probing Minggang Li(Gavin)
2024-10-16 8:38 ` [PATCH V1 3/7] net/mlx5: add new devargs to control probe optimization Minggang Li(Gavin)
2024-10-16 8:38 ` [PATCH V1 4/7] common/mlx5: fix Netlink socket leak Minggang Li(Gavin)
2024-10-16 8:38 ` [PATCH V1 5/7] common/mlx5: add RDMA monitor event awareness Minggang Li(Gavin)
2024-10-16 8:38 ` [PATCH V1 6/7] mlx5: use RDMA Netlink to update port information Minggang Li(Gavin)
2024-10-16 8:38 ` [PATCH V1 7/7] mlx5: add backward compatibility for RDMA monitor Minggang Li(Gavin)
2024-10-28 9:18 ` [PATCH V2 0/7] port probe time optimization Minggang Li(Gavin)
2024-10-28 9:18 ` [PATCH V2 1/7] mailmap: update user name Minggang Li(Gavin)
2024-10-28 9:18 ` [PATCH V2 2/7] net/mlx5: optimize device probing Minggang Li(Gavin)
2024-10-28 9:18 ` [PATCH V2 3/7] net/mlx5: add new devargs to control probe optimization Minggang Li(Gavin)
2024-10-28 15:47 ` Stephen Hemminger
2024-10-29 8:27 ` Minggang(Gavin) Li
2024-10-29 16:07 ` Stephen Hemminger
2024-10-30 8:16 ` Slava Ovsiienko
2024-10-30 19:05 ` Stephen Hemminger
2024-10-28 9:18 ` [PATCH V2 4/7] common/mlx5: fix Netlink socket leak Minggang Li(Gavin)
2024-10-28 9:18 ` [PATCH V2 5/7] common/mlx5: add RDMA monitor event awareness Minggang Li(Gavin)
2024-10-28 9:18 ` [PATCH V2 6/7] mlx5: use RDMA Netlink to update port information Minggang Li(Gavin)
2024-10-28 9:18 ` [PATCH V2 7/7] mlx5: add backward compatibility for RDMA monitor Minggang Li(Gavin)
2024-10-28 15:49 ` Stephen Hemminger
2024-10-29 8:31 ` Minggang(Gavin) Li
2024-10-29 13:42 ` [PATCH V3 0/7] port probe time optimization Minggang Li(Gavin)
2024-10-29 13:42 ` [PATCH V3 1/7] mailmap: update user name Minggang Li(Gavin)
2024-10-29 13:42 ` [PATCH V3 2/7] net/mlx5: optimize device probing Minggang Li(Gavin)
2024-10-29 13:42 ` [PATCH V3 3/7] net/mlx5: add new devargs to control probe optimization Minggang Li(Gavin)
2024-10-29 16:20 ` Stephen Hemminger
2024-10-29 13:42 ` [PATCH V3 4/7] common/mlx5: fix Netlink socket leak Minggang Li(Gavin)
2024-10-29 13:42 ` [PATCH V3 5/7] common/mlx5: add RDMA monitor event awareness Minggang Li(Gavin)
2024-10-29 13:42 ` [PATCH V3 6/7] mlx5: use RDMA Netlink to update port information Minggang Li(Gavin)
2024-10-29 13:42 ` [PATCH V3 7/7] mlx5: add backward compatibility for RDMA monitor Minggang Li(Gavin)
2024-10-29 14:31 ` [PATCH V3 0/7] port probe time optimization Minggang Li(Gavin)
2024-10-29 14:31 ` [PATCH V3 1/7] mailmap: update user name Minggang Li(Gavin)
2024-10-31 10:01 ` Raslan Darawsheh [this message]
2024-10-29 14:31 ` [PATCH V3 2/7] net/mlx5: optimize device probing Minggang Li(Gavin)
2024-10-29 14:31 ` [PATCH V3 3/7] net/mlx5: add new devargs to control probe optimization Minggang Li(Gavin)
2024-10-29 14:31 ` [PATCH V3 4/7] common/mlx5: fix Netlink socket leak Minggang Li(Gavin)
2024-10-29 14:31 ` [PATCH V3 5/7] common/mlx5: add RDMA monitor event awareness Minggang Li(Gavin)
2024-10-29 14:31 ` [PATCH V3 6/7] mlx5: use RDMA Netlink to update port information Minggang Li(Gavin)
2024-10-29 14:31 ` [PATCH V3 7/7] mlx5: add backward compatibility for RDMA monitor Minggang Li(Gavin)
2024-10-29 16:26 ` Stephen Hemminger
2024-10-30 8:25 ` Minggang(Gavin) Li
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=CH3PR12MB8460AADBE3D03E82C69268D9CF552@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=gavinl@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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;
as well as URLs for NNTP newsgroup(s).