From: Sven Barth <pascaldragon@googlemail.com>
To: Andy Walls <awalls@md.metrocast.net>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
LMML <linux-media@vger.kernel.org>
Subject: Re: Old patches sent via the Mailing list
Date: Wed, 20 Oct 2010 20:01:35 +0200 [thread overview]
Message-ID: <4CBF2E7F.6090706@googlemail.com> (raw)
In-Reply-To: <1287576040.2679.3.camel@morgan.silverblock.net>
On 20.10.2010 14:00, Andy Walls wrote:
> On Wed, 2010-10-20 at 07:19 +0200, Sven Barth wrote:
>> Am 18.10.2010 08:15, schrieb Mauro Carvalho Chehab:
>>> Em 17-10-2010 21:36, Andy Walls escreveu:
>
>>>>> The last time I sent this list, I was about to travel, and I may have missed some comments, or maybe I
>>>>> may just forgot to update. But I suspect that, for the list bellow, most of them are stuff where the
>>>>> driver maintainer just forgot at limbo.
>>>>>
>>>>>> From the list of patches under review, we have:
>>>>>
>>>>> Waiting for new patch, signed, from Sven Barth<pascaldragon@googlemail.com>
>>>>> Apr,25 2010: Problem with cx25840 and Terratec Grabster AV400 http://patchwork.kernel.org/patch/94960 Sven Barth<pascaldragon@googlemail.com>
>>>>
>>>> Sven,
>>>>
>>>> We need a "Signed-off-by: " for your submitted patch:
>>>>
>>>> http://www.linuxtv.org/wiki/index.php/Development:_Submitting_Patches#Sign_your_work
>>>>
>>>> Note, your patch has an obvious, unintentional white space change for
>>>> "if (std == V4L2_STD_NTSC_M_JP)", so could you fix that up and send a
>>>> new signed off version?
>
>>
>> Eh... I thought I had superseeded it with the patch from 10th July (mail
>> title: [PATCH] Add support for AUX_PLL on cx2583x chips). It included a
>> "Signed-of by" from me as well as "Acked by" from Mike and Andy and I
>> also excluded the whitespace change ^^
>
> Hi Sven,
>
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg20296.html
>
> So you have. How embarrassing.<:}
Well... it's a bit hard to keep the overview in this list. ;) I only saw
this thread about "old patches" by pure luck.
And thank you for digging up the link, I only had the mail version lying
around.
[And finally I won't have to patch v4l manually anymore... yippieh! I'm
looking forward to 2.6.37 :D (Good that I use a distro (ArchLinux) that
has a rolling release style ^^) ]
Regards,
Sven
next prev parent reply other threads:[~2010-10-20 18:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 21:20 Old patches sent via the Mailing list Mauro Carvalho Chehab
2010-10-17 22:03 ` Guennadi Liakhovetski
2010-10-17 23:08 ` Mauro Carvalho Chehab
2010-10-17 22:27 ` Antti Palosaari
2010-10-17 22:58 ` Mauro Carvalho Chehab
2010-10-17 23:36 ` Andy Walls
2010-10-18 6:15 ` Mauro Carvalho Chehab
2010-10-20 5:19 ` Sven Barth
2010-10-20 12:00 ` Andy Walls
2010-10-20 18:01 ` Sven Barth [this message]
2010-10-21 11:44 ` Mauro Carvalho Chehab
2010-10-18 4:27 ` Németh Márton
2010-10-18 5:28 ` Mauro Carvalho Chehab
2010-10-18 6:34 ` Jean-Francois Moine
2010-10-18 12:22 ` Mauro Carvalho Chehab
2010-10-19 18:00 ` Jarod Wilson
2010-11-12 14:43 ` [GIT PATCHES FOR 2.6.38] mantis for_2.6.38 Bjørn Mork
2010-11-13 14:26 ` Mauro Carvalho Chehab
2010-11-13 14:45 ` Bjørn Mork
2010-11-17 2:31 ` Mauro Carvalho Chehab
2010-11-17 19:43 ` Marko Ristola
2010-11-17 21:12 ` 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=4CBF2E7F.6090706@googlemail.com \
--to=pascaldragon@googlemail.com \
--cc=awalls@md.metrocast.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