From: Steven Toth <stoth@kernellabs.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PULL] http://www.kernellabs.com/hg/~stoth/saa7164-merge
Date: Thu, 17 Sep 2009 09:36:46 -0400 [thread overview]
Message-ID: <4AB23B6E.6050001@kernellabs.com> (raw)
In-Reply-To: <20090917100258.2a5269d9@pedra.chehab.org>
On 9/17/09 9:02 AM, Mauro Carvalho Chehab wrote:
> Em Thu, 03 Sep 2009 23:35:29 -0400
> Steven Toth<stoth@kernellabs.com> escreveu:
>
>> Hello Mauro,
>>
>> This patch series adds support for the NXP SAA7164 PCIe A/V bridge used by the
>> Hauppauge HVR-2200 and HVR-2250 series of products. Support is limited to DVB-T
>> / ATSC / QAM digital TV only. The driver has been in development (on and off)
>> for around a year and the KernelLabs saa7164-stable tree (from which this patch
>> set was prepared) has been in testing worldwide since approx May(?) 2009.
>>
>> The project page including links for firmware downloads, MythTV and Wiki
>> instructions is here: http://www.kernellabs.com/blog/?page_id=17
>>
>> Two general observations with the tree:
>>
>> 1. The driver is a little verbose during initial module load, I need to trim a
>> few lines of debug.
>> 2. During 64bit compile I have one compile time warning to be addressed.
>>
>> Both of these will be resolved shortly and should not stop the driver being
>> merged and made available to a much wider range of testers.
>>
>> So, please pull from http://www.kernellabs.com/hg/~stoth/saa7164-merge
>
>> SAA7164: Fix i2c eeprom read errors during load (some boards).
>> From: Steven Toth<stoth@kernellabs.com>
>> SAA7164: Fix i2c eeprom read errors during load (some boards).
>> Priority: normal
>> Signed-off-by: Steven Toth<stoth@kernellabs.com>
>
> Please don't repeat the one-line summary as description. There are several cases like the above.
>
>> - Add the SAA7164 I2C bus identifier
>
> --- a/linux/include/linux/i2c-id.h Thu Sep 03 09:06:34 2009 -0300
> +++ b/linux/include/linux/i2c-id.h Sat May 09 12:24:12 2009 -0400
>
> +#define I2C_HW_B_SAA7164 0x010024 /* NXP 7164 based tv cards */
>
> Why? Are you needing to use this constant somewhere? If not, just drop it and
> leave the field in blank.
>
> Anyway, I won't delay applying it due to that. I'm committing the series. Please send a fix
> later for the i2c-id above mentioned.
Thanks.
I should go back and check the other trees, if this field isn't required by the
i2c sub-system then I can remove it from a number of drivers. Of course, this
tree is fairly old and it may have already been done in the 23885 / cx88 /
au0828 tree's by the other devs. I'll look into this.
Regardless, I'll generate the i2c patch.
I also have another 2.6.31 related patch stacked up, once mkrufky's tree is also
merged. I'll issue both of these for merge later today.
Thanks again,
--
Steven Toth - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2009-09-17 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 3:35 [PULL] http://www.kernellabs.com/hg/~stoth/saa7164-merge Steven Toth
2009-09-06 15:11 ` Michael Krufky
2009-09-17 13:02 ` Mauro Carvalho Chehab
2009-09-17 13:36 ` Steven Toth [this message]
2009-09-17 14:20 ` Mauro Carvalho Chehab
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=4AB23B6E.6050001@kernellabs.com \
--to=stoth@kernellabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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