The patch titled cgroups: kernel/ns_cgroup.c should #include <linux/nsproxy.h> has been removed from the -mm tree. Its filename was cgroups-kernel-ns_cgroupc-should-include-linux-nsproxyh.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: cgroups: kernel/ns_cgroup.c should #include <linux/nsproxy.h> From: Adrian Bunk <bunk@xxxxxxxxxx> Every file should include the headers containing the externs its global functions (in this case for ns_cgroup_clone()). Signed-off-by: Adrian Bunk <bunk@xxxxxxxxxx> Acked-by: Serge Hallyn <serue@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- kernel/ns_cgroup.c | 1 + 1 file changed, 1 insertion(+) diff -puN kernel/ns_cgroup.c~cgroups-kernel-ns_cgroupc-should-include-linux-nsproxyh kernel/ns_cgroup.c --- a/kernel/ns_cgroup.c~cgroups-kernel-ns_cgroupc-should-include-linux-nsproxyh +++ a/kernel/ns_cgroup.c @@ -8,6 +8,7 @@ #include <linux/cgroup.h> #include <linux/fs.h> #include <linux/slab.h> +#include <linux/nsproxy.h> struct ns_cgroup { struct cgroup_subsys_state css; _ Patches currently in -mm which might be from bunk@xxxxxxxxxx are origin.patch mm-filemapc-generic_write_checks-mustnt-be-inline.patch fs-block_devc-i_bdev-mustnt-be-inline.patch frv-fix-arch-frv-mm-unalignedo-build-error.patch reiserfs-some-functions-mustnt-be-inline.patch git-acpi.patch git-x86.patch arch-x86-video-fbdevc-add-module_license.patch md-make-dm_dirty_log_initexit-static.patch drm-make-drm_minors_cleanup-static.patch git-m32r.patch net-ipv4-ip_outputc-ip_send_check-mustnt-be-inline.patch nfs-make-nfs4_drop_state_owner-static.patch git-ocfs2.patch show_schedstat-fix-memleak.patch git-sh.patch if-0-ses_match_host.patch git-watchdog.patch xen-drivers-xen-balloonc-make-a-function-static.patch make-marker_debug-static.patch reiser4.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