From: Jean Delvare <khali@linux-fr.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
LMML <linux-media@vger.kernel.org>
Subject: Re: [PATCH 2/2] V4L/DVB: Use custom I2C probing function mechanism
Date: Fri, 9 Apr 2010 09:12:49 +0200 [thread overview]
Message-ID: <20100409091249.4cc5dd6e@hyperion.delvare> (raw)
In-Reply-To: <4BBEA864.9090702@redhat.com>
Hi Mauro,
On Fri, 09 Apr 2010 01:09:08 -0300, Mauro Carvalho Chehab wrote:
> Jean Delvare wrote:
> > There are no other probing functions yet, this is the first one. I have
> > added the mechanism to i2c-core for these very IR chips.
> >
> > Putting all probe functions together would mean moving them to
> > i2c-core. This wasn't my original intent, but after all, it makes some
> > sense. Would you be happy with the following?
>
> It seems fine for me. As you're touching on i2c core and on other drivers
> on this series, I think that the better is if you could apply it on your
> tree.
Yes, this is the plan. However, before I can add them to my tree, patch
named:
[PATCH] FusionHDTV: Use quick reads for I2C IR device probing
which I posted to the linux-media mailing list some weeks ago must go
upstream. Otherwise these 2 patches do not apply cleanly.
> For both patches 1 and 2:
>
> Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Thanks.
--
Jean Delvare
next prev parent reply other threads:[~2010-04-09 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 14:14 [PATCH 2/2] V4L/DVB: Use custom I2C probing function mechanism Jean Delvare
2010-04-05 1:54 ` Andy Walls
2010-04-05 8:30 ` Jean Delvare
2010-04-05 18:26 ` Mauro Carvalho Chehab
2010-04-05 21:06 ` Jean Delvare
2010-04-06 5:34 ` Mauro Carvalho Chehab
2010-04-06 16:25 ` Jean Delvare
2010-04-09 4:09 ` Mauro Carvalho Chehab
2010-04-09 7:12 ` Jean Delvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-08 8:01 Jean Delvare
2010-06-09 15:05 ` Wolfram Sang
2010-06-09 17:39 ` Jean Delvare
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=20100409091249.4cc5dd6e@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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