From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-arch@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Nick Piggin <npiggin@suse.de>,
Christoph Lameter <clameter@sgi.com>, Mel Gorman <mel@csn.ul.ie>,
Andy Whitcroft <apw@shadowen.org>
Subject: [PATCH 0/4] vmemmap updates to V6
Date: Thu, 02 Aug 2007 10:24:33 +0100 [thread overview]
Message-ID: <exportbomb.1186045945@pinky> (raw)
Following this email are a four patches which represent the first
batch of feedback on version V5. I have some additional config
simplifications in test at the moment, and we probabally need to
move memory_model.h.
vmemmap-remove-excess-debugging -- remove some verbose and mostly
unhelpful debugging.
vmemmap-simplify-initialisation-code-and-reduce-duplication -- clean
up section initialisaion to simplify pulling out the vmemmap code.
vmemmap-pull-out-the-vmemmap-code-into-its-own-file -- pull out the
vmemmap code into its own file.
vmemmap-ppc64-convert-VMM_*-macros-to-a-real-function -- replace
some macros with an inline function to improve type safety.
The first three should be considered as fixes the patch below,
the last against the ppc64 support:
generic-virtual-memmap-support-for-sparsemem
All against 2.6.23-rc1-mm2.
Andrew please consider for -mm. (I found that merging the patch
below into its parent patch before sliding these into the tree made
the rejects must simpler.)
fix-corruption-of-memmap-on-ia64-sparsemem-when-mem_section-is-not-a-power-of-2-fix.patch
-apw
next reply other threads:[~2007-08-02 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 9:24 Andy Whitcroft [this message]
2007-08-02 9:24 ` [PATCH 1/4] vmemmap: remove excess debugging Andy Whitcroft
2007-08-02 19:18 ` Christoph Lameter
2007-08-02 9:25 ` [PATCH 2/4] vmemmap: simplify initialisation code and reduce duplication Andy Whitcroft
2007-08-02 9:25 ` [PATCH 3/4] vmemmap: pull out the vmemmap code into its own file Andy Whitcroft
2007-08-02 13:26 ` Christoph Hellwig
2007-08-02 19:28 ` Christoph Lameter
2007-08-03 14:57 ` Andy Whitcroft
2007-08-03 16:58 ` Christoph Lameter
2007-08-02 9:25 ` [PATCH 4/4] vmemmap ppc64: convert VMM_* macros to a real function Andy Whitcroft
2007-08-02 16:31 ` Dave Hansen
2007-08-02 17:39 ` Andy Whitcroft
2007-08-02 18:00 ` Dave Hansen
2007-08-02 19:30 ` Christoph Lameter
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=exportbomb.1186045945@pinky \
--to=apw@shadowen.org \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hch@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.de \
/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).