From: Alexander Kuleshov <kuleshovmail@gmail.com>
To: Russell King <linux@arm.linux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Alexander Kuleshov <kuleshovmail@gmail.com>
Subject: [PATCH 5/5 v2] arm/mmu: Use memblock_first_region_size() helper
Date: Tue, 1 Sep 2015 20:29:48 +0600 [thread overview]
Message-ID: <1441117788-30822-1-git-send-email-kuleshovmail@gmail.com> (raw)
In-Reply-To: <1441117527-30466-1-git-send-email-kuleshovmail@gmail.com>
The 0a11142e commit (mm/memblock: Introduce memblock_first_region_size()
helper) introduced memblock_first_region_size() helper for the getting
size of the first memblock region. Let's use it instead of directly access
to structure.
Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
---
arch/arm/mm/mmu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
index 870838a..fc60882 100644
--- a/arch/arm/mm/mmu.c
+++ b/arch/arm/mm/mmu.c
@@ -1176,7 +1176,7 @@ static inline void prepare_page_table(void)
/*
* Find the end of the first block of lowmem.
*/
- end = memblock.memory.regions[0].base + memblock.memory.regions[0].size;
+ end = memblock.memory.regions[0].base + memblock_first_region_size();
if (end >= arm_lowmem_limit)
end = arm_lowmem_limit;
--
2.5.0
prev parent reply other threads:[~2015-09-01 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:25 [PATCH 0/5 v2] mm/memblock: Introduce " Alexander Kuleshov
2015-09-01 14:27 ` [PATCH 1/5 " Alexander Kuleshov
2015-09-15 23:32 ` Andrew Morton
2015-09-01 14:27 ` [PATCH 2/5 v2] s390/setup: use memblock_first_region_size helper Alexander Kuleshov
2015-09-01 14:28 ` [PATCH 4/5 v2] unicore32/mmu: use memblock_first_region_size() helper Alexander Kuleshov
2015-09-01 14:29 ` Alexander Kuleshov [this message]
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=1441117788-30822-1-git-send-email-kuleshovmail@gmail.com \
--to=kuleshovmail@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®