The patch titled
Subject: fs/notify/inode_mark.c: use list_next_entry in fsnotify_unmount_inodes
has been added to the -mm tree. Its filename is
fsnotify-use-list_next_entry-in-fsnotify_unmount_inodes.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/fsnotify-use-list_next_entry-in-fsnotify_unmount_inodes.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/fsnotify-use-list_next_entry-in-fsnotify_unmount_inodes.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Geliang Tang <geliangtang@xxxxxxx>
Subject: fs/notify/inode_mark.c: use list_next_entry in fsnotify_unmount_inodes
To make the intention clearer, use list_next_entry instead of list_entry.
Signed-off-by: Geliang Tang <geliangtang@xxxxxxx>
Cc: Jan Kara <jack@xxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/notify/inode_mark.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff -puN fs/notify/inode_mark.c~fsnotify-use-list_next_entry-in-fsnotify_unmount_inodes fs/notify/inode_mark.c
--- a/fs/notify/inode_mark.c~fsnotify-use-list_next_entry-in-fsnotify_unmount_inodes
+++ a/fs/notify/inode_mark.c
@@ -199,8 +199,7 @@ void fsnotify_unmount_inodes(struct supe
break;
}
spin_unlock(&next_i->i_lock);
- next_i = list_entry(next_i->i_sb_list.next,
- struct inode, i_sb_list);
+ next_i = list_next_entry(next_i, i_sb_list);
}
/*
_
Patches currently in -mm which might be from geliangtang@xxxxxxx are
fsnotify-use-list_next_entry-in-fsnotify_unmount_inodes.patch
mm-vmalloc-use-list_nextfirst_entry.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
