public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Kevin Hilman <khilman@ti.com>
Cc: Ben Dooks <ben-linux@fluff.org>, Tony Lindgren <tony@atomide.com>,
	Andy Green <andy.green@linaro.org>,
	Lucas De Marchi <lucas.demarchi@profusion.mobi>,
	Linux I2C <linux-i2c@vger.kernel.org>,
	linux-omap@vger.kernel.org,
	davinci-linux-open-source@linux.davincidsp.com
Subject: Re: 10-bit address support in i2c-omap and i2c-davinci
Date: Mon, 7 Nov 2011 17:59:37 +0100	[thread overview]
Message-ID: <20111107175937.7099f6e9@endymion.delvare> (raw)
In-Reply-To: <87hb2g0y19.fsf@ti.com>

On Mon, 07 Nov 2011 07:09:38 -0800, Kevin Hilman wrote:
> Adding linux-omap and linux-davinci lists

Good point, sorry for missing that. Maybe the following would help?

List i2c-omap and i2c-davinci in MAINTAINERS.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
---
 MAINTAINERS |    3 +++
 1 file changed, 3 insertions(+)

--- linux-3.2-rc0.orig/MAINTAINERS	2011-11-07 17:55:46.000000000 +0100
+++ linux-3.2-rc0/MAINTAINERS	2011-11-07 17:55:55.000000000 +0100
@@ -4675,6 +4675,8 @@ Q:	http://patchwork.kernel.org/project/l
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
 S:	Maintained
 F:	arch/arm/*omap*/
+F:	drivers/i2c/busses/i2c-omap.c
+F:	include/linux/i2c-omap.h
 
 OMAP CLOCK FRAMEWORK SUPPORT
 M:	Paul Walmsley <paul@pwsan.com>
@@ -5940,6 +5942,7 @@ L:	davinci-linux-open-source@linux.davin
 Q:	http://patchwork.kernel.org/project/linux-davinci/list/
 S:	Supported
 F:	arch/arm/mach-davinci
+F:	drivers/i2c/busses/i2c-davinci.c
 
 SIS 190 ETHERNET DRIVER
 M:	Francois Romieu <romieu@fr.zoreil.com>


-- 
Jean Delvare

      reply	other threads:[~2011-11-07 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111107094614.0062a3f7@endymion.delvare>
2011-11-07 15:09 ` 10-bit address support in i2c-omap and i2c-davinci Kevin Hilman
2011-11-07 16:59   ` Jean Delvare [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=20111107175937.7099f6e9@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=andy.green@linaro.org \
    --cc=ben-linux@fluff.org \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=khilman@ti.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=tony@atomide.com \
    /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