From: Alexander Kuleshov <kuleshovmail@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>,
Pekka Enberg <penberg@kernel.org>, Mel Gorman <mgorman@suse.de>,
Xishi Qiu <qiuxishi@huawei.com>, Robin Holt <holt@sgi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alexander Kuleshov <kuleshovmail@gmail.com>
Subject: [PATCH 0/5 v2] mm/memblock: Introduce memblock_first_region_size() helper
Date: Tue, 1 Sep 2015 20:25:27 +0600 [thread overview]
Message-ID: <1441117527-30466-1-git-send-email-kuleshovmail@gmail.com> (raw)
Some architectures (like s390, microblaze and etc...) require size
of the first memory region. This patch set provides new memblock_first_region_size()
helper for this case and change usage of memblock.memory.regions[0].size on
memblock_first_region_size() for the following architectures:
* s390
* microblaze
* arm
* unicore32
Changelog:
v2:
Added changes in the architectures to the patchset.
Alexander Kuleshov (5):
mm/memblock: Introduce memblock_first_region_size() helper
s390/setup: use memblock_first_region_size helper
microblaze/mm: Use memblock_first_region_size() helper
unicore32/mmu: use memblock_first_region_size() helper
arm/mmu: Use memblock_first_region_size() helper
arch/arm/mm/mmu.c | 2 +-
arch/microblaze/mm/init.c | 6 +++---
arch/s390/kernel/setup.c | 2 +-
arch/unicore32/mm/mmu.c | 2 +-
include/linux/memblock.h | 1 +
mm/memblock.c | 5 +++++
6 files changed, 12 insertions(+), 6 deletions(-)
--
2.5.0
--
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>
next reply other threads:[~2015-09-01 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:25 Alexander Kuleshov [this message]
2015-09-01 14:27 ` [PATCH 1/5 v2] mm/memblock: Introduce memblock_first_region_size() helper Alexander Kuleshov
2015-09-15 23:32 ` Andrew Morton
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=1441117527-30466-1-git-send-email-kuleshovmail@gmail.com \
--to=kuleshovmail@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=penberg@kernel.org \
--cc=qiuxishi@huawei.com \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).