Linux Media Controller development
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: LMML <linux-media@vger.kernel.org>,
	Morimoto Kuninori <morimoto.kuninori@renesas.com>,
	Manu Abraham <abraham.manu@gmail.com>,
	Jarod Wilson <jarod@redhat.com>,
	Jean-Francois Moine <moinejf@free.fr>,
	Andy Walls <awalls@md.metrocast.net>,
	Hans de Goede <hdegoede@redhat.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Dmitri Belimov <d.belimov@gmail.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
	Pawel Osiak <pawel@osciak.co>
Subject: Re: Patches at patchwork.linuxtv.org (127 patches)
Date: Thu, 22 Sep 2011 10:26:01 -0300	[thread overview]
Message-ID: <4E7B3769.4070007@redhat.com> (raw)
In-Reply-To: <201109220817.39634.hverkuil@xs4all.nl>

Em 22-09-2011 03:17, Hans Verkuil escreveu:
> On Wednesday, September 21, 2011 22:44:20 Mauro Carvalho Chehab wrote:
>> Em 21-09-2011 17:40, Mauro Carvalho Chehab escreveu:
>>> As announced on Sept, 18, we moved our patch queue to patchwork.linuxtv.org.
>>>
>>> As we were without access to the old patchwork instance, I simply sent all
>>> emails I had locally stored on my local mahine to the new instance and reviewed
>>> all patches again. Basically, for old patches, I basically did some scripting
>>> that were marking old patches as "superseded", if they didn't apply anymore.
>>> I also preserved the patches that were marked as "under review" from patchwork
>>> time, using some scripting and a local control file.
>>>
>>> So, we're basically close to what we had before kernel.org troubles (except for
>>> a series of patches that I've already applied today).
>>>
>>> My intention is to finish review all patches marked as "new" until the end of this
>>> week, and set a new tree for linux-next with our stuff (as the old one were at
>>> git.kernel.org).
>>>
>>> Please let me know if something is missed or if some patch from the list bellow
>>> is obsolete and can be marked with a different status.
>>>
>>> Thanks!
>>> Mauro
>>>
>>>
>>> 		== New patches == 
>>
>> Gah! forgot to update the URL on my script. the patch list with the right URL is:
>>
> 
> 
>> 		== Patches for Hans Verkuil <hans.verkuil@cisco.com> check == 
>>
>> Aug, 3 2010: [1/2] TVP7002: Return V4L2_DV_INVALID if any of the errors occur.      http://patchwork.linuxtv.org/patch/4064   Mats Randgaard <mats.randgaard@tandberg.com>
>> Aug, 3 2010: [2/2] TVP7002: Changed register values.                                http://patchwork.linuxtv.org/patch/4063   Mats Randgaard <mats.randgaard@tandberg.com>
> 
> As already mentioned earlier in an email, these two can be merged. So:
> 
> Acked-by: Hans Verkuil <hans.verkuil@cisco.com>

Applied, thanks!

Mauro

  reply	other threads:[~2011-09-22 13:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 20:40 Patches at patchwork.linuxtv.org (127 patches) Mauro Carvalho Chehab
2011-09-21 20:44 ` Mauro Carvalho Chehab
2011-09-21 21:09   ` Sylwester Nawrocki
2011-09-21 22:09     ` Mauro Carvalho Chehab
2011-09-24 16:39       ` Sylwester Nawrocki
2011-09-21 21:58   ` Laurent Pinchart
2011-09-21 22:20     ` Mauro Carvalho Chehab
2011-09-21 22:40       ` Laurent Pinchart
2011-09-22  6:17   ` Hans Verkuil
2011-09-22 13:26     ` Mauro Carvalho Chehab [this message]
2011-09-22  8:21   ` Guennadi Liakhovetski
2011-09-22 13:21     ` Mauro Carvalho Chehab
2011-09-22 15:26   ` Pawel Osciak
2011-09-22 15:34     ` Mauro Carvalho Chehab
2011-09-26 11:32   ` Hiremath, Vaibhav

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=4E7B3769.4070007@redhat.com \
    --to=mchehab@redhat.com \
    --cc=abraham.manu@gmail.com \
    --cc=awalls@md.metrocast.net \
    --cc=d.belimov@gmail.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=hans.verkuil@cisco.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jarod@redhat.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    --cc=morimoto.kuninori@renesas.com \
    --cc=pawel@osciak.co \
    --cc=sakari.ailus@maxwell.research.nokia.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