From: Andy Walls <awalls@md.metrocast.net>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: LMML <linux-media@vger.kernel.org>,
"Igor M. Liplianin" <liplianin@me.by>,
Manu Abraham <abraham.manu@gmail.com>,
Jean-Francois Moine <moinejf@free.fr>,
Jarod Wilson <jarod@redhat.com>,
Richard Zidlicky <rz@linux-m68k.org>,
Antti Palosaari <crope@iki.fi>,
Sven Barth <pascaldragon@googlemail.com>,
Patrick Boettcher <pboettcher@kernellabs.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Henrik Kurelid <henke@kurelid.se>,
Hans de Goede <hdegoede@redhat.com>,
Sven Barth <pascaldragon@googlemail.com>
Subject: Re: Old patches sent via the Mailing list
Date: Sun, 17 Oct 2010 19:36:57 -0400 [thread overview]
Message-ID: <1287358617.2320.12.camel@morgan.silverblock.net> (raw)
In-Reply-To: <4CBB689F.1070100@redhat.com>
On Sun, 2010-10-17 at 19:20 -0200, Mauro Carvalho Chehab wrote:
> Hi,
>
> I did a large effort during this weekend to handle the maximum amount of patches, in order to have them
> ready for 2.6.37. While there are still some patches marked as NEW at patchwork, and a few pending pull
> requests (mostly related to more kABI changes), there are still a list of patches that are marked as
> Under review. Except for 4 patches from me, related to Doc (that I'm keeping in this list just to remind
> me that I'll need to fix them when I have some time - just some automation stuff at DocBook), all other
> patches marked as Under review are stuff that I basically depend on others.
>
> 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?
Mauro,
This patch makes obvious sense to me: don't perform audio register
updates on a chip that doesn't have an audio processing block. Sven's
approach was based on my recommended approach, after his initial
discovery on how to get his audio working.
Do we really need an S.O.B for something that appears to be common
sense, and wouldn't have been implemented any other way, even if I had
implemented it?
Regards,
Andy
next prev parent reply other threads:[~2010-10-17 23:37 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 [this message]
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
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=1287358617.2320.12.camel@morgan.silverblock.net \
--to=awalls@md.metrocast.net \
--cc=abraham.manu@gmail.com \
--cc=crope@iki.fi \
--cc=g.liakhovetski@gmx.de \
--cc=hdegoede@redhat.com \
--cc=henke@kurelid.se \
--cc=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=liplianin@me.by \
--cc=mchehab@redhat.com \
--cc=moinejf@free.fr \
--cc=pascaldragon@googlemail.com \
--cc=pboettcher@kernellabs.com \
--cc=rz@linux-m68k.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