From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [7134] linux-user: fix inotify syscalls
Date: Fri, 17 Apr 2009 13:50:33 +0000 [thread overview]
Message-ID: <E1LuoSf-00017M-RA@cvs.savannah.gnu.org> (raw)
Revision: 7134
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=7134
Author: aurel32
Date: 2009-04-17 13:50:32 +0000 (Fri, 17 Apr 2009)
Log Message:
-----------
linux-user: fix inotify syscalls
Configure test was broken, so the breakage of the #ifdef'd
code was not noticed.
Signed-off-by: Riku Voipio <riku.voipio@iki.fi>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Modified Paths:
--------------
trunk/configure
trunk/linux-user/syscall.c
Modified: trunk/configure
===================================================================
--- trunk/configure 2009-04-17 13:17:26 UTC (rev 7133)
+++ trunk/configure 2009-04-17 13:50:32 UTC (rev 7134)
@@ -1195,7 +1195,7 @@
main(void)
{
/* try to start inotify */
- return inotify_init(void);
+ return inotify_init();
}
EOF
if $cc $ARCH_CFLAGS -o $TMPE $TMPC 2> /dev/null ; then
Modified: trunk/linux-user/syscall.c
===================================================================
--- trunk/linux-user/syscall.c 2009-04-17 13:17:26 UTC (rev 7133)
+++ trunk/linux-user/syscall.c 2009-04-17 13:50:32 UTC (rev 7134)
@@ -486,6 +486,7 @@
#endif /* CONFIG_ATFILE */
#ifdef CONFIG_INOTIFY
+#include <sys/inotify.h>
#if defined(TARGET_NR_inotify_init) && defined(__NR_inotify_init)
static int sys_inotify_init(void)
@@ -502,7 +503,7 @@
#if defined(TARGET_NR_inotify_rm_watch) && defined(__NR_inotify_rm_watch)
static int sys_inotify_rm_watch(int fd, int32_t wd)
{
- return (inotify_rm_watch(fd,pathname, wd));
+ return (inotify_rm_watch(fd, wd));
}
#endif
#else
reply other threads:[~2009-04-17 13:50 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=E1LuoSf-00017M-RA@cvs.savannah.gnu.org \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).