All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [GIT PATCHES FOR 2.6.38] gspca-stv06xx: support bandwidth changing
Date: Wed, 10 Nov 2010 12:02:29 +0100	[thread overview]
Message-ID: <4CDA7BC5.30803@redhat.com> (raw)

Hi,

Here is a pull request the one patch which did not merge properly in my
previous pull request.

I based this on staging/for_v2.6.38, as that is where the patches from the
previous pull request ended up. But these are all bug-fixes intended for
2.6.37. Do I need to do anything special (like a branch based on
staging/for_v2.6.37-rc1 with all of them and a separate pull request) for
this, or will you cherry pick them over later?

The following changes since commit af9f14f7fc31f0d7b7cdf8f7f7f15a3c3794aea3:

   [media] IR: add tv power scancode to rc6 mce keymap (2010-11-10 00:58:49 -0200)

are available in the git repository at:
   git://linuxtv.org/hgoede/gspca gspca-for_v2.6.38

Hans de Goede (1):
       gspca-stv06xx: support bandwidth changing

  drivers/media/video/gspca/stv06xx/stv06xx.c        |   55 +++++++++++++++++++-
  drivers/media/video/gspca/stv06xx/stv06xx_hdcs.h   |   11 ++++-
  drivers/media/video/gspca/stv06xx/stv06xx_pb0100.c |   18 +++++--
  drivers/media/video/gspca/stv06xx/stv06xx_pb0100.h |    3 +
  drivers/media/video/gspca/stv06xx/stv06xx_sensor.h |    4 ++
  drivers/media/video/gspca/stv06xx/stv06xx_st6422.c |   17 +------
  drivers/media/video/gspca/stv06xx/stv06xx_st6422.h |    3 +
  drivers/media/video/gspca/stv06xx/stv06xx_vv6410.h |    9 ++--
  8 files changed, 93 insertions(+), 27 deletions(-)

Regards,

Hans

                 reply	other threads:[~2010-11-10 11:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CDA7BC5.30803@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.