From: Richard Purdie <rpurdie@rpsys.net>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] Fix inotify syscalls on ARM
Date: Wed, 26 Jul 2006 21:10:22 +0000 [thread overview]
Message-ID: <1153948222.10683.7.camel@localhost.localdomain> (raw)
This patch fixes the inotify syscalls on ARM so they work. It uses
__NR_SYSCALL_BASE from the libc headers (via sys/syscall.h) as this
value depends on which ABI you're using and trying to work that out gets
complicated.
Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
Index: udev-092/udev_libc_wrapper.h
=================================--- udev-092.orig/udev_libc_wrapper.h 2006-07-26 21:55:06.000000000 +0100
+++ udev-092/udev_libc_wrapper.h 2006-07-26 21:55:37.000000000 +0100
@@ -58,9 +58,9 @@
# define __NR_inotify_add_watch 152
# define __NR_inotify_rm_watch 156
#elif defined (__arm__)
-# define __NR_inotify_init 316
-# define __NR_inotify_add_watch 317
-# define __NR_inotify_rm_watch 318
+# define __NR_inotify_init __NR_SYSCALL_BASE+316
+# define __NR_inotify_add_watch __NR_SYSCALL_BASE+317
+# define __NR_inotify_rm_watch __NR_SYSCALL_BASE+318
#elif defined (__sh__)
# define __NR_inotify_init 290
# define __NR_inotify_add_watch 291
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2006-07-26 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 21:10 Richard Purdie [this message]
2006-07-27 8:56 ` [PATCH] Fix inotify syscalls on ARM Kay Sievers
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=1153948222.10683.7.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).