From: Harsha <harsha.harsha@xilinx.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <michals@xilinx.com>
Cc: <saratcha@xilinx.com>, <harshj@xilinx.com>, <git@xilinx.com>,
Harsha <harsha.harsha@xilinx.com>
Subject: [PATCH V2 4/4] MAINTAINERS: Add maintainer for Xilinx ZynqMP SHA3 driver
Date: Fri, 18 Feb 2022 00:44:24 +0530 [thread overview]
Message-ID: <1645125264-11033-5-git-send-email-harsha.harsha@xilinx.com> (raw)
In-Reply-To: <1645125264-11033-1-git-send-email-harsha.harsha@xilinx.com>
This patch adds an entry for ZynqMP SHA3 driver in the list of
Maintainers.
Signed-off-by: Harsha <harsha.harsha@xilinx.com>
---
MAINTAINERS | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ea3e6c9..6ee2441 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -21229,6 +21229,11 @@ T: git https://github.com/Xilinx/linux-xlnx.git
F: Documentation/devicetree/bindings/phy/xlnx,zynqmp-psgtr.yaml
F: drivers/phy/xilinx/phy-zynqmp.c
+XILINX ZYNQMP SHA3 DRIVER
+M: Harsha <harsha.harsha@xilinx.com>
+S: Maintained
+F: drivers/crypto/xilinx/zynqmp-sha.c
+
XILINX EVENT MANAGEMENT DRIVER
M: Abhyuday Godhasara <abhyuday.godhasara@xilinx.com>
S: Maintained
--
1.8.2.1
prev parent reply other threads:[~2022-02-17 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 19:14 [PATCH V2 0/4] crypto: Add Xilinx ZynqMP SHA3 driver support Harsha
2022-02-17 19:14 ` [PATCH V2 1/4] drivers: crypto: Updated Makefile for xilinx subdirectory Harsha
2022-02-17 19:14 ` [PATCH V2 2/4] firmware: xilinx: Add ZynqMP SHA API for SHA3 functionality Harsha
2022-02-18 9:43 ` Corentin Labbe
2022-02-21 12:17 ` Harsha Harsha
2022-02-21 13:08 ` Harsha Harsha
2022-02-22 9:47 ` Corentin Labbe
2022-02-17 19:14 ` [PATCH V2 3/4] crypto: xilinx: Add Xilinx SHA3 driver Harsha
2022-02-22 10:01 ` Corentin Labbe
2022-02-23 9:45 ` Harsha Harsha
2022-02-17 19:14 ` Harsha [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=1645125264-11033-5-git-send-email-harsha.harsha@xilinx.com \
--to=harsha.harsha@xilinx.com \
--cc=davem@davemloft.net \
--cc=git@xilinx.com \
--cc=harshj@xilinx.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=saratcha@xilinx.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
all inboxes | Powered by JetHome®