From: Amir Goldstein <amir73il@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>, Eric Paris <eparis@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/4] fsnotify: misc cleanups
Date: Sat, 17 Dec 2016 16:20:30 +0200 [thread overview]
Message-ID: <1481984434-13293-1-git-send-email-amir73il@gmail.com> (raw)
Al,
This 4 patch series is a prelude to my work on fanotify
super block watch, which is available on my github:
https://github.com/amir73il/linux/commits/fanotify_sb
I will argue for super block watch and post the patches
another time after I get more testing.
In the mean while, would you please consider these cleanup
patches. IMO, they make the code cleaner and more readable
and they should have no effect (functional and performance wise)
on existing backends.
Amir Goldstein (4):
fsnotify: pass dentry instead of inode when available
fsnotify: annotate filename events
fsnotify: simplify API for filename events
fsnotify: make MOVED_FROM a dentry event
arch/powerpc/platforms/cell/spufs/inode.c | 2 +-
fs/btrfs/ioctl.c | 2 +-
fs/debugfs/inode.c | 8 ++--
fs/devpts/inode.c | 2 +-
fs/namei.c | 23 +++++----
fs/notify/fsnotify.c | 2 +-
fs/ocfs2/refcounttree.c | 2 +-
fs/tracefs/inode.c | 4 +-
include/linux/fsnotify.h | 78 +++++++++++++++++++++----------
include/linux/fsnotify_backend.h | 3 +-
net/sunrpc/rpc_pipe.c | 6 +--
11 files changed, 82 insertions(+), 50 deletions(-)
--
2.7.4
next reply other threads:[~2016-12-17 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 14:20 Amir Goldstein [this message]
2016-12-17 14:20 ` [PATCH 1/4] fsnotify: pass dentry instead of inode when available Amir Goldstein
2016-12-17 14:20 ` [PATCH 2/4] fsnotify: annotate filename events Amir Goldstein
2016-12-17 14:20 ` [PATCH 3/4] fsnotify: simplify API for " Amir Goldstein
2016-12-17 14:20 ` [PATCH 4/4] fsnotify: make MOVED_FROM a dentry event Amir Goldstein
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=1481984434-13293-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=eparis@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.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;
as well as URLs for NNTP newsgroup(s).