From: Adrian Bunk <bunk@fs.tum.de>
To: Christer Weinigel <wingel@nano-system.com>
Cc: linux-kernel@vger.kernel.org
Subject: scx200_gpio.c doesn't compile in 2.5.50
Date: Thu, 28 Nov 2002 02:35:27 +0100 [thread overview]
Message-ID: <20021128013527.GU21307@fs.tum.de> (raw)
Compilation of drivers/char/scx200_gpio.c fails in 2.5.50 with the error
messages below.
cu
Adrian
<-- snip -->
...
gcc -Wp,-MD,drivers/char/.scx200_gpio.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=k6
-Iarch/i386/mach-generic -nostdinc -iwithprefix include -DKBUILD_BASENAME=scx200_gpio
-DKBUILD_MODNAME=scx200_gpio -c -o drivers/char/scx200_gpio.o drivers/char/scx200_gpio.c
drivers/char/scx200_gpio.c: In function `scx200_gpio_write':
drivers/char/scx200_gpio.c:31: warning: implicit declaration of function
`minor'
drivers/char/scx200_gpio.c:31: dereferencing pointer to incomplete type
drivers/char/scx200_gpio.c:34: dereferencing pointer to incomplete type
drivers/char/scx200_gpio.c: In function `scx200_gpio_read':
drivers/char/scx200_gpio.c:82: dereferencing pointer to incomplete type
drivers/char/scx200_gpio.c:85: dereferencing pointer to incomplete type
drivers/char/scx200_gpio.c: At top level:
drivers/char/scx200_gpio.c:95: warning: `struct inode' declared inside
parameter list
drivers/char/scx200_gpio.c:95: warning: its scope is only this
definition or declaration, which is probably not what you want.
drivers/char/scx200_gpio.c: In function `scx200_gpio_open':
drivers/char/scx200_gpio.c:97: dereferencing pointer to incomplete type
drivers/char/scx200_gpio.c: At top level:
drivers/char/scx200_gpio.c:103: warning: `struct inode' declared inside
parameter list
drivers/char/scx200_gpio.c:109: variable `scx200_gpio_fops' has
initializer but incomplete type
drivers/char/scx200_gpio.c:110: unknown field `owner' specified in
initializer
drivers/char/scx200_gpio.c:110: warning: excess elements in struct
initializer
drivers/char/scx200_gpio.c:110: warning: (near initialization for
`scx200_gpio_fops')
drivers/char/scx200_gpio.c:111: unknown field `write' specified in
initializer
drivers/char/scx200_gpio.c:111: warning: excess elements in struct
initializer
drivers/char/scx200_gpio.c:111: warning: (near initialization for
`scx200_gpio_fops')
drivers/char/scx200_gpio.c:112: unknown field `read' specified in
initializer
drivers/char/scx200_gpio.c:112: warning: excess elements in struct
initializer
drivers/char/scx200_gpio.c:112: warning: (near initialization for
`scx200_gpio_fops')
drivers/char/scx200_gpio.c:113: unknown field `open' specified in
initializer
drivers/char/scx200_gpio.c:113: warning: excess elements in struct
initializer
drivers/char/scx200_gpio.c:113: warning: (near initialization for
`scx200_gpio_fops')
drivers/char/scx200_gpio.c:114: unknown field `release' specified in
initializer
drivers/char/scx200_gpio.c:114: warning: excess elements in struct
initializer
drivers/char/scx200_gpio.c:114: warning: (near initialization for
`scx200_gpio_fops')
drivers/char/scx200_gpio.c: In function `scx200_gpio_init':
drivers/char/scx200_gpio.c:128: warning: implicit declaration of
function `register_chrdev'
drivers/char/scx200_gpio.c: In function `scx200_gpio_cleanup':
drivers/char/scx200_gpio.c:143: warning: implicit declaration of
function `unregister_chrdev'
make[2]: *** [drivers/char/scx200_gpio.o] Error 1
<-- snip -->
next reply other threads:[~2002-11-28 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 1:35 Adrian Bunk [this message]
2002-11-30 22:49 ` Christer Weinigel
2002-11-30 23:16 ` Arnaldo Carvalho de Melo
2002-11-30 23:35 ` Christer Weinigel
2002-11-30 23:43 ` Arnaldo Carvalho de Melo
2002-12-01 2:45 ` Alan Cox
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=20021128013527.GU21307@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wingel@nano-system.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
all inboxes | Powered by JetHome®