From: Tim Coleman <tim@epenguin.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.5.3-pre1 compiler warnings
Date: 17 Jan 2002 00:35:43 -0500 [thread overview]
Message-ID: <1011245746.3984.0.camel@tux.epenguin.org> (raw)
I noticed the following warnings when compiling 2.5.3-pre1
this evening:
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4
-c -o read_write.o read_write.c
In file included from read_write.c:13:
/usr/src/linux/include/linux/dnotify.h:18: warning: `struct inode'
declared inside parameter list
/usr/src/linux/include/linux/dnotify.h:18: warning: its scope is only
this definition or declaration, which is probably not what you want.
/usr/src/linux/include/linux/dnotify.h:21: warning: `struct inode'
declared inside parameter list
/usr/src/linux/include/linux/dnotify.h: In function `inode_dir_notify':
/usr/src/linux/include/linux/dnotify.h:23: dereferencing pointer to
incomplete type
/usr/src/linux/include/linux/dnotify.h:24: warning: passing arg 1 of
`__inode_dir_notify' from incompatible pointer type
read_write.c: In function `sys_read':
read_write.c:167: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
read_write.c: In function `sys_write':
read_write.c:194: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
read_write.c: In function `do_readv_writev':
read_write.c:299: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
read_write.c: In function `sys_pread':
read_write.c:371: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
read_write.c: In function `sys_pwrite':
read_write.c:403: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
make[2]: *** [read_write.o] Error 1
make[2]: Leaving directory `/usr/src/linux/fs'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux/fs'
make: *** [_dir_fs] Error 2
GCC version 2.95.4
--
Tim Coleman <tim@epenguin.org> [43.28 N 80.31 W]
BMath, Honours Combinatorics and Optimization, University of Waterloo
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- Benjamin Franklin
reply other threads:[~2002-01-17 5:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1011245746.3984.0.camel@tux.epenguin.org \
--to=tim@epenguin.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®