public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org, Grant Coady <lkml@dodo.com.au>
Subject: Re: Some warnings and stuff GCC 4
Date: Wed, 07 Sep 2005 22:55:18 +0200	[thread overview]
Message-ID: <431F53B6.6000805@gmail.com> (raw)
In-Reply-To: <431F292D.3070705@comcast.net>

John Richard Moser napsal(a):

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>I get lots of warnings building my kernel.  I've attached my .config;
>I'm using a kernel I downloaded from kernel.org, unpatched.
>  
>
[snip]

>. . . one of the V4L drivers failed to build too, I turned it off.
>
>
>drivers/media/video/zr36120.c: At top level:
>drivers/media/video/zr36120.c:1821: error: unknown field 'open'
>specified in initializer
>drivers/media/video/zr36120.c:1821: warning: initialization makes
>integer from pointer without a cast
>drivers/media/video/zr36120.c:1822: error: unknown field 'close'
>specified in initializer
>drivers/media/video/zr36120.c:1822: warning: initialization from
>incompatible pointer type
>drivers/media/video/zr36120.c:1823: error: unknown field 'read'
>specified in initializer
>drivers/media/video/zr36120.c:1823: warning: initialization from
>incompatible pointer type
>drivers/media/video/zr36120.c:1824: error: unknown field 'write'
>specified in initializer
>drivers/media/video/zr36120.c:1824: warning: initialization from
>incompatible pointer type
>drivers/media/video/zr36120.c:1825: error: unknown field 'poll'
>specified in initializer
>drivers/media/video/zr36120.c:1826: error: unknown field 'ioctl'
>specified in initializer
>
>  
>
<cite source="http://lkml.org/lkml/2005/7/29/302">

On Fri, 29 Jul 2005 18:40:46 -0300, Mauro Carvalho Chehab <mchehab@brturbo.com.br> wrote:
>>>>drivers/media/video/zr36120.c
>>>>drivers/media/video/zr36120_i2c.c
>>>>drivers/media/video/zr36120_mem.c
>> 
>> 
>> Being discussed on the V4L list
>	It seems that nobody are interested on maintaining it. No answer from
>V4L list subscribers.
>
>	I think it may be removed.

Please no, I'll get to it, I have one to play with.
Grant.

</cite>
So, Grant, are you doing something with that or could we schedule it for 
wiping out?

regards,

-- 
Jiri Slaby         www.fi.muni.cz/~xslaby
~\-/~      jirislaby@gmail.com      ~\-/~
241B347EC88228DE51EE A49C4A73A25004CB2A10


  reply	other threads:[~2005-09-07 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 17:53 Some warnings and stuff GCC 4 John Richard Moser
2005-09-07 20:55 ` Jiri Slaby [this message]
2005-09-08  0:25   ` Grant

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=431F53B6.6000805@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dodo.com.au \
    --cc=nigelenki@comcast.net \
    /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