public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: unlisted-recipients:; (no To-header on input)@casper.infradead.org
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [PATCH 0/8] Fix V4L/DVB/RC warnings
Date: Mon, 27 Dec 2010 14:22:50 -0200	[thread overview]
Message-ID: <20101227142250.48704ffe@gaivota> (raw)


There were several warnings at the subsystem, that were catched with
gcc version 4.5.1. All of them are fixed on those patches by a 
trivial patch. So, let's fix them ;)

Now, the only remaining patches are the ones we want to be there:

drivers/staging/lirc/lirc_i2c.c: In function ‘ir_probe’:
drivers/staging/lirc/lirc_i2c.c:431:3: warning: ‘id’ is deprecated (declared at include/linux/i2c.h:356)
drivers/staging/lirc/lirc_i2c.c:450:3: warning: ‘id’ is deprecated (declared at include/linux/i2c.h:356)
drivers/staging/lirc/lirc_i2c.c:479:9: warning: ‘id’ is deprecated (declared at include/linux/i2c.h:356)
drivers/staging/lirc/lirc_zilog.c: In function ‘ir_probe’:
drivers/staging/lirc/lirc_zilog.c:1199:2: warning: ‘id’ is deprecated (declared at include/linux/i2c.h:356)
drivers/media/video/cx88/cx88-i2c.c: In function ‘cx88_i2c_init’:
drivers/media/video/cx88/cx88-i2c.c:149:2: warning: ‘id’ is deprecated (declared at include/linux/i2c.h:356)
drivers/media/video/cx88/cx88-vp3054-i2c.c: In function ‘vp3054_i2c_probe’:
drivers/media/video/cx88/cx88-vp3054-i2c.c:128:2: warning: ‘id’ is deprecated (declared at include/linux/i2c.h:356)

They are basically caused by lirc_i2c and lirc_zilog, that still needs
to use the legacy .id field at the I2C structs. Somebody with those
hardware, please fix it.

Thanks,
Mauro

-

Mauro Carvalho Chehab (8):
  [media] dmxdev: Fix a compilation warning due to a bad type
  [media] radio-wl1273: Fix two warnings
  [media] lirc_zilog: Fix a warning
  [media] dib7000m/dib7000p: Add support for TRANSMISSION_MODE_4K
  [media] gspca: Fix a warning for using len before filling it
  [media] stv090x: Fix some compilation warnings
  [media] af9013: Fix a compilation warning
  [media] streamzap: Fix a compilation warning when compiled builtin

 drivers/media/dvb/dvb-core/dmxdev.c    |    4 ++--
 drivers/media/dvb/frontends/af9013.c   |    2 +-
 drivers/media/dvb/frontends/dib7000m.c |   10 +++++-----
 drivers/media/dvb/frontends/dib7000p.c |   10 +++++-----
 drivers/media/dvb/frontends/stv090x.c  |    6 +++---
 drivers/media/radio/radio-wl1273.c     |    3 +--
 drivers/media/rc/streamzap.c           |    2 +-
 drivers/media/video/gspca/gspca.c      |    2 +-
 drivers/staging/lirc/lirc_zilog.c      |    1 -
 9 files changed, 19 insertions(+), 21 deletions(-)

-- 
1.7.3.4


             reply	other threads:[~2010-12-27 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 16:22 Mauro Carvalho Chehab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-27 23:55 [PATCH 0/8] Fix V4L/DVB/RC warnings Andy Walls
2010-12-28  3:12 ` Mauro Carvalho Chehab
2010-12-28 14:14   ` Andy Walls
2010-12-28 14:45     ` Mauro Carvalho Chehab
2010-12-28 22:18       ` Andy Walls
2011-01-06 21:54         ` Jarod Wilson

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=20101227142250.48704ffe@gaivota \
    --to=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox