From: Robert Love <rml@novell.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
John McCutchan <ttb@tentacle.dhs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [patch 2/3] inotify: event ordering
Date: Wed, 13 Jul 2005 12:38:39 -0400 [thread overview]
Message-ID: <1121272719.6384.26.camel@betsy> (raw)
Linus,
Attached patch rearranges the event ordering for "open" to be consistent
with the ordering of the other events.
Patch is against current git tree. Please, apply.
Robert Love
Signed-off-by: Robert Love <rml@novell.com>
include/linux/fsnotify.h | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -urN linux-inotify/include/linux/fsnotify.h linux/include/linux/fsnotify.h
--- linux-inotify/include/linux/fsnotify.h 2005-07-13 11:25:31.000000000 -0400
+++ linux/include/linux/fsnotify.h 2005-07-13 11:24:27.000000000 -0400
@@ -125,8 +125,8 @@
if (S_ISDIR(inode->i_mode))
mask |= IN_ISDIR;
- inotify_inode_queue_event(inode, mask, 0, NULL);
inotify_dentry_parent_queue_event(dentry, mask, 0, dentry->d_name.name);
+ inotify_inode_queue_event(inode, mask, 0, NULL);
}
/*
reply other threads:[~2005-07-13 16:43 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=1121272719.6384.26.camel@betsy \
--to=rml@novell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=ttb@tentacle.dhs.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