From: Zaibo Xu <xuzaibo@huawei.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-crypto@vger.kernel.org>, <jonathan.cameron@huawei.com>,
<liulongfang@huawei.com>, <wangzhou1@hisilicon.com>,
<linuxarm@huawei.com>, <zhangwei375@huawei.com>,
<yekai13@huawei.com>, <forest.zhouchang@huawei.com>
Subject: [PATCH 5/5] MAINTAINERS: Add maintainer for HiSilicon SEC V2 driver
Date: Thu, 31 Oct 2019 15:35:30 +0800 [thread overview]
Message-ID: <1572507330-34502-6-git-send-email-xuzaibo@huawei.com> (raw)
In-Reply-To: <1572507330-34502-1-git-send-email-xuzaibo@huawei.com>
Here adds maintainer information for security engine driver.
Signed-off-by: Zaibo Xu <xuzaibo@huawei.com>
---
MAINTAINERS | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 536998f..bbf8985 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7372,6 +7372,16 @@ F: include/uapi/linux/if_hippi.h
F: net/802/hippi.c
F: drivers/net/hippi/
+HISILICON SECURITY ENGINE V2 DRIVER (SEC2)
+M: Zaibo Xu <xuzaibo@huawei.com>
+L: linux-crypto@vger.kernel.org
+S: Maintained
+F: drivers/crypto/hisilicon/sec2/sec_crypto.c
+F: drivers/crypto/hisilicon/sec2/sec_main.c
+F: drivers/crypto/hisilicon/sec2/sec_crypto.h
+F: drivers/crypto/hisilicon/sec2/sec.h
+F: Documentation/ABI/testing/debugfs-hisi-sec
+
HISILICON HIGH PERFORMANCE RSA ENGINE DRIVER (HPRE)
M: Zaibo Xu <xuzaibo@huawei.com>
L: linux-crypto@vger.kernel.org
--
2.8.1
prev parent reply other threads:[~2019-10-31 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 7:35 [PATCH 0/5] crypto: hisilicon - add HiSilicon SEC V2 support Zaibo Xu
2019-10-31 7:35 ` [PATCH 1/5] crypto: hisilicon - add HiSilicon SEC V2 driver Zaibo Xu
2019-10-31 7:35 ` [PATCH 2/5] crypto: hisilicon - add SRIOV for HiSilicon SEC Zaibo Xu
2019-10-31 7:35 ` [PATCH 3/5] Documentation: add DebugFS doc " Zaibo Xu
2019-10-31 7:35 ` [PATCH 4/5] crypto: hisilicon - add DebugFS " Zaibo Xu
2019-11-08 14:46 ` Herbert Xu
2019-10-31 7:35 ` Zaibo Xu [this message]
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=1572507330-34502-6-git-send-email-xuzaibo@huawei.com \
--to=xuzaibo@huawei.com \
--cc=davem@davemloft.net \
--cc=forest.zhouchang@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=jonathan.cameron@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liulongfang@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=yekai13@huawei.com \
--cc=zhangwei375@huawei.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).