All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: LMML <linux-media@vger.kernel.org>,
	Nikola Pajkovsky <npajkovs@redhat.com>
Subject: Re: Status of the patches under review at LMML (60 patches)
Date: Wed, 07 Jul 2010 02:27:38 +0300	[thread overview]
Message-ID: <4C33BBEA.5000807@iki.fi> (raw)
In-Reply-To: <4C332A5F.4000706@redhat.com>

On 07/06/2010 04:06 PM, Mauro Carvalho Chehab wrote:
> This is the summary of the patches that are currently under review at
> Linux Media Mailing List<linux-media@vger.kernel.org>.
> Each patch is represented by its submission date, the subject (up to 70
> chars) and the patchwork link (if submitted via email).
>
> P.S.: This email is c/c to the developers where some action is expected.
>        If you were copied, please review the patches, acking/nacking or
>        submitting an update.
>

> 		== Waiting for Antti Palosaari<crope@iki.fi>  review ==
>
> Mar,21 2010: af9015 : more robust eeprom parsing                                    http://patchwork.kernel.org/patch/87243

NACK, partly. I think it is rather useless.


> May,20 2010: New NXP tda18218 tuner                                                 http://patchwork.kernel.org/patch/101170

AF9015/AF9013: ACK, partly from the AF9015/AF9013 side. It is safe to 
merge, it will not break any currently supported device. But I am not 
sure if all settings are correct since I don't have suitable device 
(AF9015+TDA18218) to figure out configuration and test.

TDA18218: I don't know. I have reviewed it, feedback can be found from 
the patchwork. I don't resist to merge, but also I don't want to take 
any responsibility since I don't have this device.

regards
Antti
-- 
http://palosaari.fi/

  parent reply	other threads:[~2010-07-07  0:06 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 [this message]
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
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=4C33BBEA.5000807@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=npajkovs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.