linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Hachtmann <phacht@linux.vnet.ibm.com>
To: akpm@linux-foundation.org
Cc: hannes@cmpxchg.org, liuj97@gmail.com, santosh.shilimkar@ti.com,
	grygorii.strashko@ti.com, iamjoonsoo.kim@lge.com,
	robin.m.holt@gmail.com, tangchen@cn.fujitsu.com,
	yinghai@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	Philipp Hachtmann <phacht@linux.vnet.ibm.com>
Subject: [PATCH V5 0/3] mm/memblock: Excluded memory
Date: Mon, 20 Jan 2014 12:32:36 +0100	[thread overview]
Message-ID: <1390217559-14691-1-git-send-email-phacht@linux.vnet.ibm.com> (raw)

This all fits linux-next.

The first patch is a fix (not a replacement) to a patch that has already 
been put into linux-next. The original patch generates a warning for an
unused variable in case that CONFIG_ARCH_DISCARD_MEMBLOCK is not set.
It's now made the way Andrew suggested. 

The second patch adds support for exluded memory region handling in
memblock. This is needed by the current s390 development in conjunction
with kdump.
The patch is straightforward and adds some redundancy. This has been 
done to clarify that this patch does not intend to change any of
the current memblock API's behaviour.

The third patch does some cleanup and refactoring to memblock. It removes
the redundancies introduced by the patch before. It also is not intended
to change or break any behaviour or API of memblock.


Philipp Hachtmann (3):
  mm/nobootmem: Fix unused variable
  mm/memblock: Add support for excluded memory areas
  mm/memblock: Cleanup and refactoring after addition of nomap

 include/linux/memblock.h |  57 +++++++++---
 mm/Kconfig               |   3 +
 mm/memblock.c            | 233 +++++++++++++++++++++++++++++++++++------------
 mm/nobootmem.c           |  30 ++++--
 4 files changed, 243 insertions(+), 80 deletions(-)

-- 
1.8.4.5

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2014-01-20 11:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 11:32 Philipp Hachtmann [this message]
2014-01-20 11:32 ` [PATCH V5 1/3] mm/nobootmem: Fix unused variable Philipp Hachtmann
2014-01-20 16:28   ` Robin Holt
2014-01-21  6:16   ` David Rientjes
2014-01-21  6:57     ` Philipp Hachtmann
2014-01-21  9:51       ` David Rientjes
2014-01-20 11:32 ` [PATCH V5 2/3] mm/memblock: Add support for excluded memory areas Philipp Hachtmann
2014-01-22 11:18   ` Philipp Hachtmann
2014-01-22 20:41     ` Andrew Morton
2014-01-22 15:27   ` Robin Holt
2014-01-20 11:32 ` [PATCH V5 3/3] mm/memblock: Cleanup and refactoring after addition of nomap Philipp Hachtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1390217559-14691-1-git-send-email-phacht@linux.vnet.ibm.com \
    --to=phacht@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=grygorii.strashko@ti.com \
    --cc=hannes@cmpxchg.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuj97@gmail.com \
    --cc=robin.m.holt@gmail.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tangchen@cn.fujitsu.com \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox