From: Robert Love <rml@novell.com>
To: John McCutchan <ttb@tentacle.dhs.org>
Cc: linux-kernel@vger.kernel.org, viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [RFC][PATCH] inotify 0.9.2
Date: Tue, 21 Sep 2004 01:26:36 -0400 [thread overview]
Message-ID: <1095744396.2454.61.camel@localhost> (raw)
In-Reply-To: <1095652572.23128.2.camel@vertex>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
On Sun, 2004-09-19 at 23:56 -0400, John McCutchan wrote:
> I would appreciate design review, code review and testing.
Hi, John.
Attached patches fixes two compile warnings I receive in
drivers/char/inotify.c:
- Declaration after code in inotify_watch()
- Uncasted conversion from pointer to integer
Also, wrap some arithmetic in parenthesis, to be safe.
Best,
Robert Love
[-- Attachment #2: inotify-compile-warnings-rml-1.patch --]
[-- Type: text/x-patch, Size: 1320 bytes --]
Fix a couple misc. compile warnings in inotify.c
Signed-Off-By: Robert Love <rml@novell.com>
drivers/char/inotify.c | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
--- linux-inotify/drivers/char/inotify.c 2004-09-21 00:58:03.912389824 -0400
+++ linux/drivers/char/inotify.c 2004-09-21 01:24:07.042757888 -0400
@@ -45,7 +45,7 @@
#define MAX_INOTIFY_QUEUED_EVENTS 256 /* Only the first Z events will be queued */
#define __BITMASK_SIZE (MAX_INOTIFY_DEV_WATCHERS / 8)
-#define INOTIFY_DEV_TIMER_TIME jiffies + (HZ/4)
+#define INOTIFY_DEV_TIMER_TIME (jiffies + (HZ/4))
static atomic_t watcher_count; // < MAX_INOTIFY_DEVS
@@ -668,7 +668,7 @@
file->private_data = dev;
- dev->timer.data = dev;
+ dev->timer.data = (unsigned long) dev;
dev->timer.function = inotify_dev_timer;
dev->timer.expires = INOTIFY_DEV_TIMER_TIME;
@@ -745,8 +745,10 @@
* watching, we just update the mask and return 0
*/
if (inotify_dev_is_watching_inode (dev, inode)) {
- iprintk(INOTIFY_DEBUG_ERRORS, "adjusting event mask for inode %p\n", inode);
- struct inotify_watcher *owatcher; // the old watcher
+ struct inotify_watcher *owatcher; /* the old watcher */
+
+ iprintk(INOTIFY_DEBUG_ERRORS,
+ "adjusting event mask for inode %p\n", inode);
owatcher = inode_find_dev (inode, dev);
next prev parent reply other threads:[~2004-09-21 5:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 3:56 [RFC][PATCH] inotify 0.9.2 John McCutchan
2004-09-20 21:52 ` Robert Love
2004-09-21 5:21 ` Robert Love
2004-09-21 15:34 ` Edgar Toernig
2004-09-21 15:43 ` Chris Friesen
2004-09-22 2:27 ` John McCutchan
2004-09-23 1:46 ` Ray Lee
2004-09-23 3:42 ` John McCutchan
2004-09-23 4:52 ` Ray Lee
2004-09-23 5:10 ` Robert Love
2004-09-23 5:29 ` Ray Lee
2004-09-21 15:46 ` Robert Love
2004-09-21 5:26 ` Robert Love [this message]
2004-09-21 5:44 ` Robert Love
2004-09-21 16:04 ` Robert Love
2004-09-21 18:56 ` Robert Love
2004-09-21 20:55 ` Robert Love
2004-09-22 2:32 ` John McCutchan
2004-09-22 3:49 ` Robert Love
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=1095744396.2454.61.camel@localhost \
--to=rml@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ttb@tentacle.dhs.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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