The patch titled Subject: hfsplus: remove useless check has been added to the -mm tree. Its filename is hfsplus-remove-useless-check.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: Artem Bityutskiy <artem.bityutskiy@xxxxxxxxxxxxxxx> Subject: hfsplus: remove useless check This check is useless because we always have 'sb->s_fs_info' to be non-NULL. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@xxxxxxxxxxxxxxx> Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/hfsplus/super.c | 3 --- 1 file changed, 3 deletions(-) diff -puN fs/hfsplus/super.c~hfsplus-remove-useless-check fs/hfsplus/super.c --- a/fs/hfsplus/super.c~hfsplus-remove-useless-check +++ a/fs/hfsplus/super.c @@ -240,9 +240,6 @@ static void hfsplus_put_super(struct sup dprint(DBG_SUPER, "hfsplus_put_super\n"); - if (!sb->s_fs_info) - return; - if (!(sb->s_flags & MS_RDONLY) && sbi->s_vhdr) { struct hfsplus_vh *vhdr = sbi->s_vhdr; _ Subject: Subject: hfsplus: remove useless check Patches currently in -mm which might be from artem.bityutskiy@xxxxxxxxxxxxxxx are linux-next.patch hfs-push-lock_super-down.patch hfs-get-rid-of-lock_super.patch hfs-remove-extra-mdb-write-on-unmount.patch hfs-simplify-a-bit-checking-for-r-o.patch hfs-introduce-vfs-superblock-object-back-reference.patch hfs-get-rid-of-hfs_sync_super.patch hfs-get-rid-of-hfs_sync_super-checkpatch-fixes.patch hfsplus-make-hfsplus_sync_fs-static.patch hfsplus-amend-debugging-print.patch hfsplus-remove-useless-check.patch hfsplus-get-rid-of-write_super.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