[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1358855181-6160-1-git-send-email-tangchen@cn.fujitsu.com>
Date: Tue, 22 Jan 2013 19:46:17 +0800
From: Tang Chen <tangchen@...fujitsu.com>
To: akpm@...ux-foundation.org, rientjes@...gle.com,
len.brown@...el.com, benh@...nel.crashing.org, paulus@...ba.org,
cl@...ux.com, minchan.kim@...il.com,
kosaki.motohiro@...fujitsu.com, isimatu.yasuaki@...fujitsu.com,
wujianguo@...wei.com, wency@...fujitsu.com, hpa@...or.com,
linfeng@...fujitsu.com, laijs@...fujitsu.com, mgorman@...e.de,
yinghai@...nel.org, glommer@...allels.com, jiang.liu@...wei.com,
julian.calaby@...il.com, sfr@...b.auug.org.au
Cc: x86@...nel.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-acpi@...r.kernel.org
Subject: [PATCH Bug fix 0/4] Bug fix for movablecore_map boot option.
Hi Andrew,
patch1 ~ patch3 fix some problems of movablecore_map boot option.
And since the name "core" could be confused, patch4 rename this option
to movablemem_map.
All these patches are based on the latest -mm tree.
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm
Tang Chen (4):
Bug fix: Use CONFIG_HAVE_MEMBLOCK_NODE_MAP to protect movablecore_map
in memblock_overlaps_region().
Bug fix: Fix the doc format.
Bug fix: Remove the unused sanitize_zone_movable_limit() definition.
Rename movablecore_map to movablemem_map.
Documentation/kernel-parameters.txt | 8 +-
include/linux/memblock.h | 3 +-
include/linux/mm.h | 8 +-
mm/memblock.c | 42 +++++++++++-
mm/page_alloc.c | 116 +++++++++++++++++-----------------
5 files changed, 106 insertions(+), 71 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists