linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: mingo@redhat.com, hpa@zytor.com, tglx@linutronix.de,
	benh@kernel.crashing.org, yinghai@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, x86@kernel.org
Subject: [PATCHSET x86/mm] memblock, x86: Misc cleanups
Date: Tue, 12 Jul 2011 09:58:04 +0200	[thread overview]
Message-ID: <1310457490-3356-1-git-send-email-tj@kernel.org> (raw)

Hello,

This patchset contains the following six cleanup patches in generic
and x86 memblock code paths.  All the changes in this function are
more or less trivial.  This prepares for further memblock updates.

 0001-x86-Fix-memblock_x86_check_reserved_size-use-in-efi_.patch
 0002-bootmem-Fix-__free_pages_bootmem-to-use-order-proper.patch
 0003-memblock-Use-MEMBLOCK_ALLOC_ACCESSIBLE-instead-of-AN.patch
 0004-memblock-Use-round_up-down-instead-of-memblock_align.patch
 0005-memblock-Kill-MEMBLOCK_ERROR.patch
 0006-memblock-Replace-memblock_find_base-with-memblock_fi.patch

This patchset is on top of

  x86/urgent (5da0ef9a85 "x86: Disable AMD_NUMA for 32bit for now")
+ pfn->nid granularity check patches [1]

and available in the following git branch.

 git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git review-x86-mm-prep

diffstat follows.

 arch/x86/kernel/aperture_64.c |    2 -
 arch/x86/kernel/check.c       |    2 -
 arch/x86/kernel/e820.c        |    2 -
 arch/x86/kernel/setup.c       |    4 +-
 arch/x86/kernel/trampoline.c  |    2 -
 arch/x86/mm/init.c            |    2 -
 arch/x86/mm/memblock.c        |    6 ++--
 arch/x86/mm/numa.c            |    6 ++--
 arch/x86/mm/numa_32.c         |    4 +-
 arch/x86/mm/numa_emulation.c  |    2 -
 arch/x86/platform/efi/efi.c   |    3 --
 include/linux/memblock.h      |    7 ++--
 kernel/printk.c               |    2 -
 mm/memblock.c                 |   63 +++++++++++++++---------------------------
 mm/nobootmem.c                |    2 -
 mm/page_alloc.c               |    8 ++---
 16 files changed, 49 insertions(+), 68 deletions(-)

--
tejun

[1] http://thread.gmane.org/gmane.linux.kernel/1166521

             reply	other threads:[~2011-07-12  7:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12  7:58 Tejun Heo [this message]
2011-07-12  7:58 ` [PATCH 1/6] x86: Fix memblock_x86_check_reserved_size() use in efi_reserve_boot_services() Tejun Heo
2011-07-12  7:58   ` Tejun Heo
2011-07-12  7:58 ` [PATCH 2/6] bootmem: Fix __free_pages_bootmem() to use @order properly Tejun Heo
2011-07-12  7:58   ` Tejun Heo
2011-07-12  7:58 ` [PATCH 3/6] memblock: Use MEMBLOCK_ALLOC_ACCESSIBLE instead of ANYWHERE in memblock_alloc_try_nid() Tejun Heo
2011-07-12  7:58   ` Tejun Heo
2011-07-12  7:58 ` [PATCH 4/6] memblock: Use round_up/down() instead of memblock_align_up/down() Tejun Heo
2011-07-12  7:58   ` Tejun Heo
2011-07-12  7:58 ` [PATCH 5/6] memblock: Kill MEMBLOCK_ERROR Tejun Heo
2011-07-12  7:58   ` Tejun Heo
2011-07-12  7:58 ` [PATCH 6/6] memblock: Replace memblock_find_base() with memblock_find_in_range() Tejun Heo
2011-07-12  7:58   ` Tejun Heo

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=1310457490-3356-1-git-send-email-tj@kernel.org \
    --to=tj@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=hpa@zytor.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).