From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] MAINTAINERS: catch special Rockchip code locations
Date: Wed, 27 Aug 2014 00:05:50 +0200 [thread overview]
Message-ID: <3644024.F4LLe7dWA4@diego> (raw)
Add some more locations that aren't catched by the general wildcard.
This includes the devicetree files, clock directory, rk3x i2c driver,
everything in a third layer under drivers like iio/adc/rockchip_saradc.c
and the i2s driver.
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
---
Main reason behind this, is that I only accidentially stumbled over the
clock api refactoring series [0] from Toneu Vizoso, wheras with the
better matching it should've been automatic.
[0] https://lkml.org/lkml/2014/8/18/481
This could either go into 3.17 as fix, or could be queued for 3.18
[resent, as I forgot the linux-rockchip list, sorry for the noise]
MAINTAINERS | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c2ecffb..2f66c46 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1279,8 +1279,13 @@ M: Heiko Stuebner <heiko@sntech.de>
L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
L: linux-rockchip at lists.infradead.org
S: Maintained
+F: arch/arm/boot/dts/rk3*
F: arch/arm/mach-rockchip/
+F: drivers/clk/rockchip/
+F: drivers/i2c/busses/i2c-rk3x.c
F: drivers/*/*rockchip*
+F: drivers/*/*/*rockchip*
+F: sound/soc/rockchip/
ARM/SAMSUNG ARM ARCHITECTURES
M: Ben Dooks <ben-linux@fluff.org>
--
2.0.1
next reply other threads:[~2014-08-26 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 22:05 Heiko Stübner [this message]
2014-08-27 22:13 ` [PATCH RESEND] MAINTAINERS: catch special Rockchip code locations Olof Johansson
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=3644024.F4LLe7dWA4@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).