From: Baoyou Xie <baoyou.xie@linaro.org>
To: andy.shevchenko@gmail.com, jun.nie@linaro.org,
baoyou.xie@linaro.org, wsa@the-dreams.de, robh+dt@kernel.org,
mark.rutland@arm.com
Cc: linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 2/3] MAINTAINERS: add zx2967 i2c controller driver to ARM ZTE architecture
Date: Mon, 6 Feb 2017 11:26:08 +0800 [thread overview]
Message-ID: <1486351569-4814-2-git-send-email-baoyou.xie@linaro.org> (raw)
In-Reply-To: <1486351569-4814-1-git-send-email-baoyou.xie@linaro.org>
Add the zx2967 i2c controller driver as maintained by ARM ZTE
architecture maintainers, as they're parts of the core IP.
Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5fb9b62..4e81e2b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1987,10 +1987,12 @@ L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm/mach-zx/
F: drivers/clk/zte/
+F: drivers/i2c/busses/i2c-zx2967.c
F: drivers/reset/reset-zx2967.c
F: drivers/soc/zte/
F: Documentation/devicetree/bindings/arm/zte.txt
F: Documentation/devicetree/bindings/clock/zx296702-clk.txt
+F: Documentation/devicetree/bindings/i2c/i2c-zx2967.txt
F: Documentation/devicetree/bindings/reset/zte,zx2967-reset.txt
F: Documentation/devicetree/bindings/soc/zte/
F: include/dt-bindings/soc/zx*.h
--
2.7.4
next prev parent reply other threads:[~2017-02-06 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 3:26 [PATCH v4 1/3] dt: bindings: add documentation for zx2967 family i2c controller Baoyou Xie
2017-02-06 3:26 ` Baoyou Xie [this message]
[not found] ` <1486351569-4814-1-git-send-email-baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-06 3:26 ` [PATCH v4 3/3] i2c: zx2967: add i2c controller driver for ZTE's zx2967 family Baoyou Xie
2017-02-06 3:28 ` Baoyou Xie
2017-02-07 7:11 ` Shawn Guo
2017-02-07 10:09 ` Jun Nie
2017-02-07 10:47 ` Andy Shevchenko
2017-02-08 6:30 ` Baoyou Xie
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=1486351569-4814-2-git-send-email-baoyou.xie@linaro.org \
--to=baoyou.xie@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--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).