From: Ben Dooks <ben-linux@fluff.org>
To: Uwe Kleine-K??nig <u.kleine-koenig@pengutronix.de>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Jean Delvare <khali@linux-fr.org>,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH] MAINTAINERS: add i2c tree for embedded platforms
Date: Tue, 26 Jan 2010 14:37:03 +0000 [thread overview]
Message-ID: <20100126143703.GB12774@fluff.org.uk> (raw)
In-Reply-To: <1264411234-5400-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Mon, Jan 25, 2010 at 10:20:34AM +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.)
We might be able to add each driver individually, but that would mean
updating the entry with each driver added, and that sounds too much
like hard work (sorry, receipie for merge conflict)
> 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/
> --
> 1.6.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
prev parent reply other threads:[~2010-01-26 14:37 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
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 [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=20100126143703.GB12774@fluff.org.uk \
--to=ben-linux@fluff.org \
--cc=khali@linux-fr.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