From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: [PATCH] maintainers: update email address
Date: Wed, 21 Sep 2022 14:41:01 +0100 [thread overview]
Message-ID: <20220921134101.4165351-1-ferruh.yigit@amd.com> (raw)
Updating @xilinx.com domain to @amd.com domain.
Signed-off-by: Ferruh Yigit <ferruh.yigit@amd.com>
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 32ffdd1a61ca..0fc5c8dfe583 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -28,7 +28,7 @@ M: David Marchand <david.marchand@redhat.com>
T: git://dpdk.org/dpdk
Next-net Tree
-M: Ferruh Yigit <ferruh.yigit@xilinx.com>
+M: Ferruh Yigit <ferruh.yigit@amd.com>
M: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
T: git://dpdk.org/next/dpdk-next-net
@@ -405,7 +405,7 @@ F: app/test/test_mbuf.c
Ethernet API
M: Thomas Monjalon <thomas@monjalon.net>
-M: Ferruh Yigit <ferruh.yigit@xilinx.com>
+M: Ferruh Yigit <ferruh.yigit@amd.com>
M: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
T: git://dpdk.org/next/dpdk-next-net
F: lib/ethdev/
@@ -588,7 +588,7 @@ F: drivers/bus/vmbus/
Networking Drivers
------------------
-M: Ferruh Yigit <ferruh.yigit@xilinx.com>
+M: Ferruh Yigit <ferruh.yigit@amd.com>
T: git://dpdk.org/next/dpdk-next-net
F: doc/guides/nics/features/default.ini
--
2.25.1
next reply other threads:[~2022-09-21 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 13:41 Ferruh Yigit [this message]
2022-09-28 12:12 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2023-10-20 8:51 Chenbo Xia
2023-10-20 9:04 ` Maxime Coquelin
2023-10-20 10:54 ` David Marchand
2023-09-19 3:44 Chenbo Xia
2023-09-20 7:08 ` Maxime Coquelin
2023-09-20 15:39 ` Patrick Robb
2023-09-21 11:41 ` David Marchand
2022-04-21 15:20 Konstantin Ananyev
2022-04-21 16:04 ` Mcnamara, John
2022-05-10 9:07 ` Thomas Monjalon
2022-04-11 18:05 Ferruh Yigit
2022-04-14 9:44 ` 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=20220921134101.4165351-1-ferruh.yigit@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--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).