From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, wsa@the-dreams.de,
linux-i2c@vger.kernel.org, nicolas.ferre@microchip.com,
Tudor Ambarus <tudor.ambarus@microchip.com>
Subject: [PATCH 3/3] MAINTAINERS: add a maintainer for Microchip / Atmel ECC driver
Date: Wed, 5 Jul 2017 13:08:00 +0300 [thread overview]
Message-ID: <1499249280-31779-4-git-send-email-tudor.ambarus@microchip.com> (raw)
In-Reply-To: <1499249280-31779-1-git-send-email-tudor.ambarus@microchip.com>
A new cryptographic engine driver was added in
drivers/crypto/atmel-ecc.*.
Add myself as a maintainer for this driver.
Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
---
MAINTAINERS | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a24eb8c..d55b983 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8464,6 +8464,12 @@ F: drivers/dma/at_hdmac.c
F: drivers/dma/at_hdmac_regs.h
F: include/linux/platform_data/dma-atmel.h
+MICROCHIP / ATMEL ECC DRIVER
+M: Tudor Ambarus <tudor.ambarus@microchip.com>
+L: linux-crypto@vger.kernel.org
+S: Maintained
+F: drivers/crypto/atmel-ecc.*
+
MICROCHIP / ATMEL ISC DRIVER
M: Songjun Wu <songjun.wu@microchip.com>
L: linux-media@vger.kernel.org
--
2.7.4
next prev parent reply other threads:[~2017-07-05 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 10:07 [PATCH 0/3] crypto: introduce Microchip / Atmel ECC driver Tudor Ambarus
2017-07-05 10:07 ` [PATCH 1/3] crypto: kpp: add get/set_flags helpers Tudor Ambarus
2017-07-05 10:07 ` [PATCH 2/3] crypto: introduce Microchip / Atmel ECC driver Tudor Ambarus
2017-07-05 10:08 ` Tudor Ambarus [this message]
2017-07-05 10:54 ` [PATCH 0/3] " Marcel Holtmann
2017-07-05 11:44 ` Tudor Ambarus
2017-07-05 12:26 ` Marcel Holtmann
2017-07-18 10:38 ` Herbert Xu
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=1499249280-31779-4-git-send-email-tudor.ambarus@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=wsa@the-dreams.de \
/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).