The patch titled Subject: fs/debugsfs: remove unnecessary inode->i_private initialization has been added to the -mm tree. Its filename is fs-debugsfs-remove-unnecessary-inode-i_private-initialization.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: Yan Hong <clouds.yan@xxxxxxxxx> Subject: fs/debugsfs: remove unnecessary inode->i_private initialization inode->i_private is promised to be NULL on allocation, no need to set it explicitly. Signed-off-by: Yan Hong <clouds.yan@xxxxxxxxx> Cc: Greg KH <greg@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/debugfs/inode.c | 1 - 1 file changed, 1 deletion(-) diff -puN fs/debugfs/inode.c~fs-debugsfs-remove-unnecessary-inode-i_private-initialization fs/debugfs/inode.c --- a/fs/debugfs/inode.c~fs-debugsfs-remove-unnecessary-inode-i_private-initialization +++ a/fs/debugfs/inode.c @@ -59,7 +59,6 @@ static struct inode *debugfs_get_inode(s case S_IFDIR: inode->i_op = &simple_dir_inode_operations; inode->i_fop = &simple_dir_operations; - inode->i_private = NULL; /* directory inodes start off with i_nlink == 2 * (for "." entry) */ _ Patches currently in -mm which might be from clouds.yan@xxxxxxxxx are fs-debugsfs-remove-unnecessary-inode-i_private-initialization.patch fs-block_devc-need-not-to-check-inode-i_bdev-in-bd_forget.patch proc-return-enomem-when-inode-allocation-failed.patch proc-no-need-to-initialize-proc_inode-fd-in-proc_get_inode.patch proc-use-kzalloc-instead-of-kmalloc-and-memset.patch proc-use-kzalloc-instead-of-kmalloc-and-memset-fix.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