The patch titled Subject: mm: memory_hotplug: no need to check res twice in add_memory has been added to the -mm tree. Its filename is mm-memory_hotplug-no-need-to-check-res-twice-in-add_memory.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: Sasha Levin <sasha.levin@xxxxxxxxxx> Subject: mm: memory_hotplug: no need to check res twice in add_memory Remove one redundant check of res. Signed-off-by: Sasha Levin <sasha.levin@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/memory_hotplug.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff -puN mm/memory_hotplug.c~mm-memory_hotplug-no-need-to-check-res-twice-in-add_memory mm/memory_hotplug.c --- a/mm/memory_hotplug.c~mm-memory_hotplug-no-need-to-check-res-twice-in-add_memory +++ a/mm/memory_hotplug.c @@ -901,8 +901,7 @@ error: /* rollback pgdat allocation and others */ if (new_pgdat) rollback_node_hotadd(nid, pgdat); - if (res) - release_memory_resource(res); + release_memory_resource(res); out: unlock_memory_hotplug(); _ Patches currently in -mm which might be from sasha.levin@xxxxxxxxxx are linux-next.patch watchdog-trigger-all-cpu-backtrace-when-locked-up-and-going-to-panic.patch mm-huge_memory-use-new-hashtable-implementation.patch mm-memory_hotplug-no-need-to-check-res-twice-in-add_memory.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