The patch titled Subject: mm/mmu_notifier: init notifier if necessary has been removed from the -mm tree. Its filename was mm-mmu_notifier-init-notifier-if-necessary-v2.patch This patch was dropped because it was folded into mm-mmu_notifier-init-notifier-if-necessary.patch ------------------------------------------------------ From: Gavin Shan <shangw@xxxxxxxxxxxxxxxxxx> Subject: mm/mmu_notifier: init notifier if necessary v2: Use GFP_KERNEL instead of GFP_ATOMIC when allocating the MMU notifier_mm as Andrew suggested. Signed-off-by: Gavin Shan <shangw@xxxxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/mmu_notifier.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN mm/mmu_notifier.c~mm-mmu_notifier-init-notifier-if-necessary-v2 mm/mmu_notifier.c --- a/mm/mmu_notifier.c~mm-mmu_notifier-init-notifier-if-necessary-v2 +++ a/mm/mmu_notifier.c @@ -215,7 +215,7 @@ static int do_mmu_notifier_register(stru if (!mm_has_notifiers(mm)) { mmu_notifier_mm = kmalloc(sizeof(struct mmu_notifier_mm), - GFP_ATOMIC); + GFP_KERNEL); if (unlikely(!mmu_notifier_mm)) { ret = -ENOMEM; goto out_of_mem; _ Patches currently in -mm which might be from shangw@xxxxxxxxxxxxxxxxxx are origin.patch mm-mmu_notifier-init-notifier-if-necessary.patch mm-vmscan-fix-error-number-for-failed-kthread.patch mm-memblock-use-existing-interface-to-set-nid.patch mm-memblock-cleanup-early_node_map-related-comments.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