From: Sriram Dash <sriram.dash@samsung.com>
To: linux-kernel@vger.kernel.org, mkl@pengutronix.de,
linux-can@vger.kernel.org, wg@grandegger.com
Cc: mchehab+samsung@kernel.org, davem@davemloft.net,
gregkh@linuxfoundation.org, robh@kernel.org, dmurphy@ti.com,
rcsekar@samsung.com, pankaj.dubey@samsung.com,
pankj.sharma@samsung.com, Sriram Dash <sriram.dash@samsung.com>
Subject: [PATCH] MAINTAINERS: add myself as maintainer of MCAN MMIO device driver
Date: Tue, 3 Dec 2019 09:59:09 +0530 [thread overview]
Message-ID: <1575347349-32689-1-git-send-email-sriram.dash@samsung.com> (raw)
In-Reply-To: CGME20191203043533epcas5p19bfc21e2b03db7f27c6d84cda6824d27@epcas5p1.samsung.com
Since we are actively working on MMIO MCAN device driver,
as discussed with Marc, I am adding myself as a maintainer.
Signed-off-by: Sriram Dash <sriram.dash@samsung.com>
---
MAINTAINERS | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index fc36fe5..64ecf11 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10082,6 +10082,15 @@ W: https://linuxtv.org
S: Maintained
F: drivers/media/radio/radio-maxiradio*
+MCAN MMIO DEVICE DRIVER
+M: Sriram Dash <sriram.dash@samsung.com>
+L: linux-can@vger.kernel.org
+S: Maintained
+F: Documentation/devicetree/bindings/net/can/m_can.txt
+F: drivers/net/can/m_can/m_can_platform.c
+F: drivers/net/can/m_can/m_can.c
+F: drivers/net/can/m_can/m_can.h
+
MCP4018 AND MCP4531 MICROCHIP DIGITAL POTENTIOMETER DRIVERS
M: Peter Rosin <peda@axentia.se>
L: linux-iio@vger.kernel.org
--
2.7.4
next parent reply other threads:[~2019-12-03 4:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191203043533epcas5p19bfc21e2b03db7f27c6d84cda6824d27@epcas5p1.samsung.com>
2019-12-03 4:29 ` Sriram Dash [this message]
2019-12-03 9:55 ` [PATCH] MAINTAINERS: add myself as maintainer of MCAN MMIO device driver Marc Kleine-Budde
2019-12-05 17:42 ` Dan Murphy
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=1575347349-32689-1-git-send-email-sriram.dash@samsung.com \
--to=sriram.dash@samsung.com \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mkl@pengutronix.de \
--cc=pankaj.dubey@samsung.com \
--cc=pankj.sharma@samsung.com \
--cc=rcsekar@samsung.com \
--cc=robh@kernel.org \
--cc=wg@grandegger.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).