The patch titled
Subject: mm-cma-release-trigger-fix
has been removed from the -mm tree. Its filename was
mm-cma-release-trigger-fixpatch.patch
This patch was dropped because it was folded into mm-cma-release-trigger.patch
------------------------------------------------------
From: Michal Hocko <mhocko@xxxxxxx>
Subject: mm-cma-release-trigger-fix
allmodconfig fails with
mm/cma_debug.c: In function `cma_free_mem':
mm/cma_debug.c:71:4: error: invalid use of undefined type `struct page'
mem->p += count;
Fix it by including mm_types.h
Signed-off-by: Michal Hocko <mhocko@xxxxxxx>
Cc: Sasha Levin <sasha.levin@xxxxxxxxxx>
Cc: Fengguang Wu <fengguang.wu@xxxxxxxxx>
Cc: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/cma_debug.c | 1 +
1 file changed, 1 insertion(+)
diff -puN mm/cma_debug.c~mm-cma-release-trigger-fixpatch mm/cma_debug.c
--- a/mm/cma_debug.c~mm-cma-release-trigger-fixpatch
+++ a/mm/cma_debug.c
@@ -10,6 +10,7 @@
#include <linux/list.h>
#include <linux/kernel.h>
#include <linux/slab.h>
+#include <linux/mm_types.h>
#include "cma.h"
_
Patches currently in -mm which might be from mhocko@xxxxxxx are
mm-hugetlb-use-pmd_page-in-follow_huge_pmd.patch
mm-memcontrol-update-copyright-notice.patch
mm-cma-release-trigger.patch
mm-hide-per-cpu-lists-in-output-of-show_mem.patch
mm-completely-remove-dumping-per-cpu-lists-from-show_mem.patch
mm-refactor-do_wp_page-extract-the-reuse-case.patch
mm-refactor-do_wp_page-rewrite-the-unlock-flow.patch
mm-refactor-do_wp_page-extract-the-page-copy-flow.patch
mm-refactor-do_wp_page-handling-of-shared-vma-into-a-function.patch
mm-clarify-__gfp_nofail-deprecation-status.patch
mm-clarify-__gfp_nofail-deprecation-status-checkpatch-fixes.patch
sparc-clarify-__gfp_nofail-allocation.patch
mm-memcontrol-let-mem_cgroup_move_account-have-effect-only-if-mmu-enabled.patch
memcg-print-cgroup-information-when-system-panics-due-to-panic_on_oom.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
