From: Mike Shettel <mshettel@codeaurora.org>
To: gregkh@linuxfoundation.org, boris.brezillon@bootlin.com,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org
Cc: Mike Shettel <mshettel@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, evgreen@chromium.org,
acourbot@chromium.org, swboyd@chromium.org,
dianders@chromium.org, mka@chromium.org,
bjorn.andersson@linaro.org
Subject: [PATCH v1 3/3] MAINTAINERS: Add Qualcomm Generic Interface I3C driver maintainer
Date: Tue, 31 Jul 2018 23:39:02 -0600 [thread overview]
Message-ID: <1533101942-29442-4-git-send-email-mshettel@codeaurora.org> (raw)
In-Reply-To: <1533101942-29442-1-git-send-email-mshettel@codeaurora.org>
Signed-off-by: Mike Shettel <mshettel@codeaurora.org>
---
MAINTAINERS | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 622327b..775829c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10943,6 +10943,14 @@ L: netdev@vger.kernel.org
S: Supported
F: drivers/net/ethernet/qualcomm/emac/
+QUALCOMM GENERIC INTERFACE I3C DRIVER
+M: Alok Chauhan <alokc@codeaurora.org>
+M: Mike Shettel <mshettel@codeaurora.org>
+L: linux-i2c@vger.kernel.org
+L: linux-arm-msm@vger.kernel.org
+S: Supported
+F: drivers/i3c/master/i3c-master-qcom-geni.c
+
QUALCOMM HEXAGON ARCHITECTURE
M: Richard Kuo <rkuo@codeaurora.org>
L: linux-hexagon@vger.kernel.org
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2018-08-01 5:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 5:38 [PATCH v1 0/3] Add a driver for Qualcomm GENI I3C master IP Mike Shettel
2018-08-01 5:39 ` [PATCH v1 1/3] i3c: master: " Mike Shettel
2018-08-09 15:18 ` Stephen Boyd
2018-08-01 5:39 ` [PATCH v1 2/3] dt-bindings: i3c: Document Qualcomm GENI I3C master bindings Mike Shettel
2018-08-09 15:06 ` Stephen Boyd
2018-08-13 21:47 ` Rob Herring
2018-08-01 5:39 ` Mike Shettel [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=1533101942-29442-4-git-send-email-mshettel@codeaurora.org \
--to=mshettel@codeaurora.org \
--cc=acourbot@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=boris.brezillon@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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).