From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PULL FOR v3.7] uvcvideo patches
Date: Tue, 21 Aug 2012 07:18:17 -0300 [thread overview]
Message-ID: <50336069.4030402@redhat.com> (raw)
In-Reply-To: <1561599.3DnS2US7L9@avalon>
Em 21-08-2012 06:13, Laurent Pinchart escreveu:
> Hi Mauro,
>
> On Sunday 12 August 2012 17:25:05 Laurent Pinchart wrote:
>> Hi Mauro,
>>
>> The following changes since commit 518c267f4ca4c45cc51bd582b4aef9f0b9f01eba:
>>
>> [media] saa7164: use native print_hex_dump() instead of custom one
>> (2012-08-12 07:58:54 -0300)
>>
>> are available in the git repository at:
>> git://linuxtv.org/pinchartl/uvcvideo.git uvcvideo-next
>>
>> Jayakrishnan Memana (1):
>> uvcvideo: Reset the bytesused field when recycling an erroneous buffer
>
> This patch made it to your media-next tree, but not to the main media tree,
> while the other three patches in this pull request did. Is there a specific
> reason for that ?
This one is on my queue for 3.6. I should be sending the pull request for it
likely today. Due to the tree reorg, the -next pull from my tree failed
last week.
Regards,
Mauro
>
>> Laurent Pinchart (2):
>> uvcvideo: Support super speed endpoints
>> uvcvideo: Add support for Ophir Optronics SPCAM 620U cameras
>>
>> Stefan Muenzel (1):
>> uvcvideo: Support 10bit, 12bit and alternate 8bit greyscale formats
>>
>> drivers/media/video/uvc/uvc_driver.c | 28 ++++++++++++++++++++++++++--
>> drivers/media/video/uvc/uvc_queue.c | 1 +
>> drivers/media/video/uvc/uvc_video.c | 30 ++++++++++++++++++++++++------
>> drivers/media/video/uvc/uvcvideo.h | 9 +++++++++
>> 4 files changed, 60 insertions(+), 8 deletions(-)
>
prev parent reply other threads:[~2012-08-21 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 15:25 [GIT PULL FOR v3.7] uvcvideo patches Laurent Pinchart
2012-08-21 9:13 ` Laurent Pinchart
2012-08-21 10:18 ` Mauro Carvalho Chehab [this message]
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=50336069.4030402@redhat.com \
--to=mchehab@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).