public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@linuxtv.org>
To: Linux and Kernel Video <video4linux-list@redhat.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	Andrew Morton <akpm@osdl.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Axel Thimm <Axel.Thimm@ATrpms.net>
Subject: Re: bttv-driver.c:3964: error: void value not ignored as it ought to be
Date: Mon, 17 Jul 2006 15:53:20 -0400	[thread overview]
Message-ID: <44BBEAB0.3080105@linuxtv.org> (raw)
In-Reply-To: <20060717124505.GD7281@neu.nirvana>

Axel Thimm wrote:
> latest hg fails on > 2.6.17 due to video_device_create_file being void
> but still being asked for a return value in bttv-driver.c
> 
> linux/drivers/media/video/bt8xx/bttv-driver.c:
> 
>    3963 #if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,17)
>    3964         ret = video_device_create_file(btv->video_dev, &class_device_attr_card);
>    3965         if (ret < 0)
> 
> 
> linux/include/media/v4l2-dev.h:
> 
>     379 static inline void
>     380 video_device_create_file(struct video_device *vfd,
>     381                          struct class_device_attribute *attr)
>     382 {
> 
>   CC [M]  /builddir/video4linux-20060717/v4l/flexcop-dma.o
>   CC [M]  /builddir/video4linux-20060717/v4l/bttv-driver.o
> /builddir/video4linux-20060717/v4l/bttv-driver.c: In function 'bttv_register_video':
> /builddir/video4linux-20060717/v4l/bttv-driver.c:3964: error: void value not ignored as it ought to be
> /builddir/video4linux-20060717/v4l/bttv-driver.c: In function 'bttv_probe':
> /builddir/video4linux-20060717/v4l/bttv-driver.c:4074: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'resource_size_t'
> /builddir/video4linux-20060717/v4l/bttv-driver.c:4086: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'
> make[3]: *** [/builddir/video4linux-20060717/v4l/bttv-driver.o] Error 1

Hmmm... This was caused by the "Check all __must_check warnings in
bttv." patch from Randy Dunlap (cc's from original thread added)

I am aware that this was done for various reasons of sanity checking,
however, we cannot check the return value of a void ;-)

-Mike
-- 
Michael Krufky


       reply	other threads:[~2006-07-17 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060717124505.GD7281@neu.nirvana>
2006-07-17 19:53 ` Michael Krufky [this message]
2006-07-17 20:55   ` bttv-driver.c:3964: error: void value not ignored as it ought to be Nish Aravamudan
2006-07-17 21:30     ` Michael Krufky
2006-07-18  3:03       ` Michael Krufky
2006-07-18  3:30 Randy Dunlap

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=44BBEAB0.3080105@linuxtv.org \
    --to=mkrufky@linuxtv.org \
    --cc=Axel.Thimm@ATrpms.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=rdunlap@xenotime.net \
    --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