LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-dvb-maintainer@linuxtv.org, video4linux-list@redhat.com,
	linux-kernel@vger.kernel.org
Subject: [GIT PATCHES] V4L/DVB fixes
Date: Mon, 20 Aug 2007 16:55:19 -0300	[thread overview]
Message-ID: <1187640017.565.24.camel@gaivota> (raw)

Linus,

Please pull from:
        ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git master

For the following:

   - A few ivtv fixes;
   - Updates firmware location for tda10046;
   - Some fixes for OLPC camera;
   - Sets the proper frequency limits on dvb-pll.

Cheers,
Mauro.

---

 Documentation/dvb/get_dvb_firmware    |   24 +++++++++++-----------
 drivers/media/dvb/frontends/dvb-pll.c |    2 +-
 drivers/media/video/cafe_ccic.c       |   35 ++++++++++++++++++++++++++++++--
 drivers/media/video/ivtv/ivtv-ioctl.c |    3 +-
 drivers/media/video/ov7670.c          |    5 +++-
 include/linux/videodev2.h             |    2 -
 6 files changed, 51 insertions(+), 20 deletions(-)

Andreas Arens (1):
      V4L/DVB (6016): get_dvb_firmware: update script for new location of tda10046 firmware

Chris Ball (1):
      V4L/DVB (6026): Avoid powering up the camera on resume

Hans Verkuil (3):
      V4L/DVB (5968): videodev2.h: remove superfluous FBUF GLOBAL_INV_ALPHA support
      V4L/DVB (5967): ivtv: fix VIDIOC_S_FBUF:new OSD values where never set
      V4L/DVB (5969): ivtv: report ivtv version in status log

Jonathan Corbet (1):
      V4L/DVB (6027): Get rid of an ill-behaved msleep in i2c write

Marcelo Tosatti (1):
      V4L/DVB (6028): Turn an unnecessary mdelay() into msleep().

Trent Piepho (1):
      V4L/DVB (5991): dvb-pll: Set minimum and maximum frequency properly

---------------------------------------------------
V4L/DVB development is hosted at http://linuxtv.org


             reply	other threads:[~2007-08-20 20:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 19:55 Mauro Carvalho Chehab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-12 21:02 [GIT PATCHES] V4L/DVB fixes Mauro Carvalho Chehab
2008-01-11 21:42 Mauro Carvalho Chehab
2008-01-07  9:38 Mauro Carvalho Chehab
2008-01-09 15:43 ` Hans-Peter Jansen
2008-01-09 18:30   ` Mauro Carvalho Chehab
2007-12-13 22:45 Mauro Carvalho Chehab
2007-12-12  1:05 Mauro Carvalho Chehab
2007-11-04 23:18 Mauro Carvalho Chehab
2007-10-17 17:17 Mauro Carvalho Chehab
2007-09-14 16:41 Mauro Carvalho Chehab
2007-08-23 17:04 Mauro Carvalho Chehab
2007-07-30 19:15 Mauro Carvalho Chehab
2007-07-03 19:20 Mauro Carvalho Chehab
2007-06-09 11:13 Mauro Carvalho Chehab
2007-05-13 16:38 Mauro Carvalho Chehab
2007-03-26  3:36 Mauro Carvalho Chehab
2007-03-26 21:55 ` Linus Torvalds
2007-03-27 11:57   ` Mauro Carvalho Chehab
2007-03-27 16:24     ` Linus Torvalds

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=1187640017.565.24.camel@gaivota \
    --to=mchehab@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=video4linux-list@redhat.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;
as well as URLs for NNTP newsgroup(s).