From: Hans de Goede <hdegoede@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [GIT PATCHES FOR 3.1] pwc: Add support for control events
Date: Tue, 19 Jul 2011 12:44:31 +0200 [thread overview]
Message-ID: <4E25600F.6020500@redhat.com> (raw)
In-Reply-To: <4E255D71.8050906@redhat.com>
Hi,
On 07/19/2011 12:33 PM, Hans de Goede wrote:
> Hi Mauro,
>
> Please pull from my tree to add support for control events to
> the pwc driver. Note that this patch depends upon the patches
> from hverkuils poll tree (and those patches are thus also
> in my tree, but not part of this pull req).
>
> The following changes since commit 30178e8623281063c18592a848cdcd71f78f603d:
>
> vivi: let vb2_poll handle events. (2011-07-18 13:07:28 +0200)
>
> are available in the git repository at:
> git://linuxtv.org/hgoede/gspca.git media-for_v3.1
>
> Hans de Goede (1):
> pwc: Add support for control events
>
Self NACK, I just noticed that I got the release / unregister handling
wrong. Will re do and re-submit a pull req later.
Regards,
Hans
prev parent reply other threads:[~2011-07-19 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 10:33 [GIT PATCHES FOR 3.1] pwc: Add support for control events Hans de Goede
2011-07-19 10:44 ` Hans de Goede [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=4E25600F.6020500@redhat.com \
--to=hdegoede@redhat.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 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.