From: Fiona Trahe <fiona.trahe@intel.com>
To: dev@dpdk.org
Cc: arkadiuszx.kusztal@intel.com
Subject: [dpdk-dev] [PATCH] Adding maintainers for Intel QAT PMD
Date: Fri, 5 Feb 2016 16:36:01 +0000 [thread overview]
Message-ID: <1454690161-25566-1-git-send-email-fiona.trahe@intel.com> (raw)
Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
---
MAINTAINERS | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index b90aeea..748197f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -353,6 +353,9 @@ M: Declan Doherty <declan.doherty@intel.com>
F: drivers/crypto/aesni_mb/
Intel QuickAssist
+M: John Griffin <john.griffin@intel.com>
+M: Fiona Trahe <fiona.trahe@intel.com>
+M: Deepak Kumar Jain <deepak.k.jain@intel.com>
F: drivers/crypto/qat/
--
1.7.0.7
next reply other threads:[~2016-02-05 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 16:36 Fiona Trahe [this message]
2016-02-29 18:18 ` John Griffin
2016-02-29 18:24 ` Jain, Deepak K
2016-03-11 0:36 ` 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=1454690161-25566-1-git-send-email-fiona.trahe@intel.com \
--to=fiona.trahe@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
/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).