The patch titled iget-stop-ext2-from-using-iget-and-read_inode-try-checkpatch-fixes has been removed from the -mm tree. Its filename was iget-stop-ext2-from-using-iget-and-read_inode-try-checkpatch-fixes.patch This patch was dropped because it was folded into iget-stop-ext2-from-using-iget-and-read_inode-try.patch The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: iget-stop-ext2-from-using-iget-and-read_inode-try-checkpatch-fixes From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> WARNING: no space between function name and open parenthesis '(' #31: FILE: fs/ext2/ext2.h:127: +extern struct inode *ext2_iget (struct super_block *, unsigned long); WARNING: no space between function name and open parenthesis '(' #43: FILE: fs/ext2/inode.c:1188: +struct inode *ext2_iget (struct super_block *sb, unsigned long ino) ERROR: "foo * bar" should be "foo *bar" #50: FILE: fs/ext2/inode.c:1192: + struct ext2_inode * raw_inode; total: 1 errors, 2 warnings, 161 lines checked Your patch has style problems, please review. If any of these errors are false positives report them to the maintainer, see CHECKPATCH in MAINTAINERS. Please run checkpatch prior to sending patches Cc: "Theodore Ts'o" <tytso@xxxxxxx> Cc: <linux-ext4@xxxxxxxxxxxxxxx> Cc: David Howells <dhowells@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/ext2/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN fs/ext2/inode.c~iget-stop-ext2-from-using-iget-and-read_inode-try-checkpatch-fixes fs/ext2/inode.c --- a/fs/ext2/inode.c~iget-stop-ext2-from-using-iget-and-read_inode-try-checkpatch-fixes +++ a/fs/ext2/inode.c @@ -1185,7 +1185,7 @@ struct inode *ext2_iget (struct super_bl { struct ext2_inode_info *ei; struct buffer_head * bh; - struct ext2_inode * raw_inode; + struct ext2_inode *raw_inode; struct inode *inode; long ret = -EIO; int n; _ Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are origin.patch vfs-swap-do_ioctl-and-vfs_ioctl-names.patch cgroup-simplify-space-stripping.patch memory-controller-memory-accounting-v7.patch memory-controller-add-per-container-lru-and-reclaim-v7.patch memory-controller-oom-handling-v7.patch memory-controller-add-switch-to-control-what-type-of-pages-to-limit-v7.patch memcontrol-move-mm_cgroup-to-header-file.patch memcontrol-move-oom-task-exclusion-to-tasklist.patch memory-cgroup-enhancements-fix-zone-handling-in-try_to_free_mem_cgroup_page.patch memory-cgroup-enhancements-add-status-accounting-function-for-memory-cgroup.patch memory-cgroup-enhancements-add-memorystat-file.patch per-zone-and-reclaim-enhancements-for-memory-controller-take-3-remember-reclaim-priority-in-memory-cgroup.patch per-zone-and-reclaim-enhancements-for-memory-controller-take-3-modifies-vmscanc-for-isolate-globa-cgroup-lru-activity.patch cgroups-mechanism-to-process-each-task-in-a-cgroup.patch hotplug-cpu-move-tasks-in-empty-cpusets-to-parent.patch cpusets-update_cpumask-revision.patch drivers-edac-add-marvell-mv64x60-driver.patch introduce-flags-for-reserve_bootmem.patch iget-stop-affs-from-using-iget-and-read_inode-try.patch iget-stop-efs-from-using-iget-and-read_inode-try.patch iget-stop-ext2-from-using-iget-and-read_inode-try.patch iget-stop-ext2-from-using-iget-and-read_inode-try-checkpatch-fixes.patch iget-stop-ext3-from-using-iget-and-read_inode-try-checkpatch-fixes.patch iget-stop-freevxfs-from-using-iget-and-read_inode-checkpatch-fixes.patch iget-stop-the-minix-filesystem-from-using-iget-and-checkpatch-fixes.patch iget-stop-procfs-from-using-iget-and-read_inode-checkpatch-fixes.patch iget-stop-qnx4-from-using-iget-and-read_inode-try-checkpatch-fixes.patch iget-stop-romfs-from-using-iget-and-read_inode-checkpatch-fixes.patch iget-stop-the-sysv-filesystem-from-using-iget-and-checkpatch-fixes.patch iget-stop-ufs-from-using-iget-and-read_inode-try-checkpatch-fixes.patch iget-stop-hostfs-from-using-iget-and-read_inode-checkpatch-fixes.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