From: Jean Delvare <khali@linux-fr.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH] MAINTAINERS: add i2c tree for embedded platforms
Date: Mon, 25 Jan 2010 11:10:55 +0100 [thread overview]
Message-ID: <20100125111055.05ccedf2@hyperion.delvare> (raw)
In-Reply-To: <1264411234-5400-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Mon, 25 Jan 2010 10:20:34 +0100, Uwe Kleine-König wrote:
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> Cc: Ben Dooks <ben-linux@fluff.org>
> ---
> Hello,
>
> I wonder if it makes sence to split the "I2C SUBSYSTEM" entry into
> something like:
>
> I2C SUBSYSTEM (PC drivers, core)
> M: Jean Delvare <khali@linux-fr.org>
> L: ...
> W: ...
> T: quilt ...
> S: ...
> F: Documentation/i2c/
> F: drivers/i2c/
> F: include/linux/i2c.h
> F: include/linux/i2c-*.h
>
> I2C SUBSYSTEM (embedded platforms)
> M: Ben Dooks <ben-linux@fluff.org>
> L: ...
> W: ...
> T: git ...
> S: ...
> F: drivers/i2c/
> F: include/linux/i2c-*.h
>
> (I'm not entirely sure about the file patterns for the 2nd entry.)
I'm not sure what value it adds, compared to having a single entry as
we have today. scripts/get_maintainer.pl will produce the same output,
won't it?
This script (and our minds) being directory-driven, I suspect that the
only efficient way to split the entries would be to first move all i2c bus
driver for embedded platforms to a separate subdirectory. I'm leaving
it to Ben and the embedded community to decide whether they want to do
that or not.
>
> Best regards
> Uwe
>
> MAINTAINERS | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1858646..a1813fd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2629,6 +2629,7 @@ M: "Ben Dooks (embedded platforms)" <ben-linux@fluff.org>
> L: linux-i2c@vger.kernel.org
> W: http://i2c.wiki.kernel.org/
> T: quilt kernel.org/pub/linux/kernel/people/jdelvare/linux-2.6/jdelvare-i2c/
> +T: git git://git.fluff.org/bjdooks/linux.git
> S: Maintained
> F: Documentation/i2c/
> F: drivers/i2c/
Yes, please!
Acked-by: Jean Delvare <khali@linux-fr.org>
--
Jean Delvare
next prev parent reply other threads:[~2010-01-25 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 9:20 [PATCH] MAINTAINERS: add i2c tree for embedded platforms Uwe Kleine-König
2010-01-25 10:10 ` Jean Delvare [this message]
2010-01-26 14:38 ` Ben Dooks
2010-01-26 15:25 ` Jean Delvare
2010-01-26 15:37 ` Wolfram Sang
2010-01-26 16:34 ` Jean Delvare
2010-01-26 14:37 ` Ben Dooks
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=20100125111055.05ccedf2@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=ben-linux@fluff.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.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