From: Sven Barth <pascaldragon@googlemail.com>
To: LMML <linux-media@vger.kernel.org>
Cc: Mike Isely <isely@isely.net>, Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: Status of the patches under review at LMML (60 patches)
Date: Fri, 09 Jul 2010 21:39:19 +0200 [thread overview]
Message-ID: <4C377AE7.9070404@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1007072223310.14650@ivanova.isely.net>
Hi!
On 08.07.2010 05:31, Mike Isely wrote:
> These are cx25840 patches and I'm not the maintainer of that module. I
> can't really speak to the correctness of the changes. Best I can do is
> to try the patch with a few pvrusb2-driven devices here that use the
> cx25840 module. I've done that now (HVR-1950 and PVR-USB2 model 24012)
> and everything continues to work fine.
I also retested the patch (with the recent v4l changes) and my device
continues to work as expected (using your current snapshot from July,
Mike :) ).
> Note, this part of the patch:
>
> int hw_fix = state->pvr150_workaround;
> -
> - if (std == V4L2_STD_NTSC_M_JP) {
> + if (std == V4L2_STD_NTSC_M_JP) {
> /* Japan uses EIAJ audio standard */
> cx25840_write(client, 0x808, hw_fix ? 0x2f : 0xf7);
> } else if (std == V4L2_STD_NTSC_M_KR) {
>
> is a whitespace-only change which introduces a bogus tab and messes up
> the indentation of that opening if-statement. It should probably be
> removed from the patch.
I wonder how that came in there... my excuses for this (and also the
removed new line some lines below that).
> Other than that, you have my ack:
>
> Acked-By: Mike Isely<isely@pobox.com>
>
> -Mike
>
>
Hmm... I've read a bit in the wiki about submitting patches and read
that one should sign-off his/her patches... as I didn't do that back
then (as I thought that patch would be open for discussion ^^ - note to
self: add RFC next time), should I resend the patch with a comment and
the sign-off (and excluding the indentation mistake) or should I just
send a sign-off in reference to this patch? Or something else?
Regards,
Sven
next prev parent reply other threads:[~2010-07-09 19:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 13:06 Status of the patches under review at LMML (60 patches) Mauro Carvalho Chehab
2010-07-06 13:13 ` Laurent Pinchart
2010-07-06 14:47 ` Mauro Carvalho Chehab
2010-07-06 13:53 ` Steven Toth
2010-07-06 17:52 ` Mauro Carvalho Chehab
2010-07-06 15:03 ` Uwe Kleine-König
2010-07-06 15:21 ` Randy Dunlap
2010-07-06 17:31 ` Mauro Carvalho Chehab
2010-07-06 17:36 ` Randy Dunlap
2010-07-06 15:38 ` Jean-Francois Moine
2010-07-06 23:27 ` Antti Palosaari
2010-07-07 5:51 ` Bee Hock Goh
2010-07-07 11:45 ` Sven Barth
2010-07-07 15:57 ` Mike Isely
2010-07-08 3:31 ` Mike Isely
2010-07-09 19:39 ` Sven Barth [this message]
2010-07-10 15:57 ` Mauro Carvalho Chehab
2010-07-08 22:03 ` Tobias Lorenz
2010-07-10 12:59 ` Andy Walls
-- strict thread matches above, loose matches on Subject: below --
2010-07-12 4:20 Henrik Kurelid
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=4C377AE7.9070404@googlemail.com \
--to=pascaldragon@googlemail.com \
--cc=isely@isely.net \
--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