From: Jianfeng Tan <jianfeng.tan@intel.com>
To: dev@dpdk.org
Cc: thomas.monjalon@6wind.com, bruce.richardson@intel.com,
yuanhan.liu@linux.intel.com,
Jianfeng Tan <jianfeng.tan@intel.com>
Subject: [dpdk-dev] [PATCH] maintainers: claim responsability for xen
Date: Mon, 7 Nov 2016 07:38:46 +0000 [thread overview]
Message-ID: <1478504326-68105-1-git-send-email-jianfeng.tan@intel.com> (raw)
As some users are still using xen as the hypervisor, I suggest to
continue support for xen in DPDK. And from 16.11, I will be the
maintainer of all xen-related files.
Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ba12d1b..d2fa2db 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -190,6 +190,7 @@ M: Anatoly Burakov <anatoly.burakov@intel.com>
F: lib/librte_eal/linuxapp/eal/*vfio*
Linux Xen
+M: Jianfeng Tan <jianfeng.tan@intel.com>
F: lib/librte_eal/linuxapp/xen_dom0/
F: lib/librte_eal/linuxapp/eal/*xen*
F: lib/librte_eal/linuxapp/eal/include/exec-env/rte_dom0_common.h
--
2.7.4
next reply other threads:[~2016-11-07 7:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 7:38 Jianfeng Tan [this message]
2016-11-09 22:03 ` Thomas Monjalon
2016-11-10 18:59 ` Konrad Rzeszutek Wilk
2016-11-10 20:49 ` Tan, Jianfeng
2017-02-16 11:06 ` Thomas Monjalon
2017-02-16 13:02 ` Vincent JARDIN
2017-02-16 13:36 ` Konrad Rzeszutek Wilk
2017-02-16 16:17 ` Jan Blunck
2017-02-16 21:51 ` Vincent JARDIN
2017-02-17 16:07 ` Konrad Rzeszutek Wilk
2017-02-20 9:56 ` Jan Blunck
2017-02-20 17:36 ` Joao Martins
2017-02-20 15:33 ` Joao Martins
2017-02-23 8:49 ` Thomas Monjalon
2017-02-23 20:10 ` Martinx - ジェームズ
2017-05-04 22:04 ` Thomas Monjalon
2017-05-11 11:41 ` Tan, Jianfeng
2017-06-19 13:22 ` 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=1478504326-68105-1-git-send-email-jianfeng.tan@intel.com \
--to=jianfeng.tan@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=yuanhan.liu@linux.intel.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).