Em 24-11-2011 07:26, Patrick Boettcher escreveu:
> Hi Mauro,
> 
> On Tue, 4 Oct 2011, Patrick Boettcher wrote:
> 
>> Hi Mauro,
>>
>> if it's not too late for 3.2 could you please pull from
>>
>> git://linuxtv.org/pb/media_tree.git staging/for_v3.2
>>
>> for
>>
>> [media] dib9090: limit the I2C speed [media] dib8096P: add the reference 
>> board [media] add the support for DiBcom [media] dib7090: add the reference 
>> board [media] DiB8000: improve the tuning and the SNR monitoring
>> [media] DiBcom: correct warnings
>> [media] dib7090: add the reference board TFE7090E
>> [media] dib7000p/dib0090: update the driver
> 
> I think this PULL request got lost. (as usual for my pull-requests :( ).

Yes, I didn't get your pull request. Now that we're using patchwork, to also 
track pull
requests, it is easy for you to check if the pull request is on my queue. Just 
take a
look at http://patchwork.linuxtv.org.

It should be noticed that patchwork relies on the way that git request-pull 
formats the
message:

$  git request-pull HEAD^1 .
The following changes since commit db9bc660cf4d1a09565f5db2bab9d3b86e3e32a5:

  [media] ir-rc6-decoder: Support RC6-6A variable length data (2011-11-23 
22:23:15 -0200)

are available in the git repository at:
  . staging/for_v3.3

Dan Carpenter (1):
      [media] V4L: mt9t112: use after free in mt9t112_probe()

 drivers/media/video/mt9t112.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

It basically seeks for "The following...at: <url> <branch>" part of the 
message. If found,
it will add it at its repository, like:

        http://patchwork.linuxtv.org/patch/8279/

> It was meant for 3.2 and was sent in advance.
> 
> Do you think you will get it in?

We can get the fixes, and new board additions for 3.2, but driver updates should
go to 3.3.

> 
> regards,
> -- 
> 
> Patrick Boettcher - Kernel Labs
> http://www.kernellabs.com/

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to