From: lauraa@codeaurora.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 0/2] Remove ARM meminfo
Date: Thu, 3 Apr 2014 10:04:56 -0700 [thread overview]
Message-ID: <1396544698-15596-1-git-send-email-lauraa@codeaurora.org> (raw)
Hi,
This is v5 of the series to remove meminfo and use memblock
directly. This has been validated with/without highmem although
SPARSEMEM has not been validated. Reviews/testing welcome.
Thanks,
Laura
v5: Folded in patch from Nicolas, addressed several issues found by
Russell with fixes suggested by Grygorii. Whitespace cleanup.
v4: Added nommu support. Fixed issues with !HIGHMEM per Grygorii Strashko.
v3: Fixed compilation issue for CONFIG_SPARSEMEM. Fixed several typos
in spitz.c. Removed early_init_dt_add_memory_arch per Grant's suggestion.
v2: Implemented full commandline support for mem at addr
Laura Abbott (2):
mm/memblock: add memblock_get_current_limit
arm: Get rid of meminfo
arch/arm/Kconfig | 5 --
arch/arm/boot/compressed/atags_to_fdt.c | 2 +
arch/arm/include/asm/mach/arch.h | 4 +-
arch/arm/include/asm/memblock.h | 3 +-
arch/arm/include/asm/setup.h | 28 --------
arch/arm/kernel/atags_parse.c | 5 +-
arch/arm/kernel/devtree.c | 5 --
arch/arm/kernel/setup.c | 30 +++-----
arch/arm/mach-clps711x/board-clep7312.c | 7 +-
arch/arm/mach-clps711x/board-edb7211.c | 10 ++-
arch/arm/mach-clps711x/board-p720t.c | 2 +-
arch/arm/mach-footbridge/cats-hw.c | 2 +-
arch/arm/mach-footbridge/netwinder-hw.c | 2 +-
arch/arm/mach-msm/board-halibut.c | 6 --
arch/arm/mach-msm/board-mahimahi.c | 13 ++--
arch/arm/mach-msm/board-msm7x30.c | 3 +-
arch/arm/mach-msm/board-sapphire.c | 13 ++--
arch/arm/mach-msm/board-trout.c | 8 +--
arch/arm/mach-orion5x/common.c | 3 +-
arch/arm/mach-orion5x/common.h | 3 +-
arch/arm/mach-pxa/cm-x300.c | 3 +-
arch/arm/mach-pxa/corgi.c | 10 ++-
arch/arm/mach-pxa/eseries.c | 9 ++-
arch/arm/mach-pxa/poodle.c | 8 +--
arch/arm/mach-pxa/spitz.c | 8 +--
arch/arm/mach-pxa/tosa.c | 8 +--
arch/arm/mach-realview/core.c | 11 ++-
arch/arm/mach-realview/core.h | 3 +-
arch/arm/mach-realview/realview_pb1176.c | 8 +--
arch/arm/mach-realview/realview_pbx.c | 17 ++---
arch/arm/mach-s3c24xx/mach-smdk2413.c | 8 +--
arch/arm/mach-s3c24xx/mach-vstms.c | 8 +--
arch/arm/mach-sa1100/assabet.c | 2 +-
arch/arm/mm/init.c | 72 ++++++++-----------
arch/arm/mm/mmu.c | 117 +++++++++----------------------
arch/arm/mm/nommu.c | 66 +++++++++--------
include/linux/memblock.h | 2 +
mm/memblock.c | 5 ++
38 files changed, 186 insertions(+), 333 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2014-04-03 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 17:04 Laura Abbott [this message]
2014-04-03 17:04 ` [PATCHv5 2/2] arm: Get rid of meminfo Laura Abbott
2014-05-01 13:08 ` Grant Likely
2014-05-06 16:33 ` Laura Abbott
2014-06-23 9:17 ` Uwe Kleine-König
2014-06-23 9:30 ` Uwe Kleine-König
2014-06-23 20:47 ` Laura Abbott
2014-06-24 8:49 ` Uwe Kleine-König
2014-06-27 9:21 ` Laura Abbott
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=1396544698-15596-1-git-send-email-lauraa@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).