From: Andy Whitcroft <apw@shadowen.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Andrew Morton <akpm@osdl.org>,
linux-arch@vger.kernel.org, Dave Hansen <haveblue@us.ibm.com>,
Matt Tolentino <matthew.e.tolentino@intel.com>,
Bob Picco <bob.picco@hp.com>
Subject: Re: sparsemem patches in -mm
Date: Tue, 21 Jun 2005 16:51:13 +0100 [thread overview]
Message-ID: <42B83771.1050304@shadowen.org> (raw)
In-Reply-To: <20050621141755.GX11655@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> On Tue, Jun 21, 2005 at 02:13:52AM -0700, Andrew Morton wrote:
>
>>Could I ask the arch maintainers to review the `sparsemem' patches from -mm,
>>please, if you haven't done so...
>>
>>They're all in http://www.zip.com.au/~akpm/linux/patches/stuff/sparsemem/
>
>
> Pretty confusing. All kinds of options added, removed, modified, put
> back ... let's merge it, then see how it looks. Maybe we'll switch
> parisc from discontigmem to sparsemem.
Would it make sense for me to take the current pile of patches in -mm
and merge the fixes into the appropriate main patches to make a
consolidated patch set? If we want to do that I am happy to put the
effort in.
-apw
next prev parent reply other threads:[~2005-06-21 15:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 9:13 sparsemem patches in -mm Andrew Morton
2005-06-21 9:50 ` Andi Kleen
2005-06-21 10:09 ` Andrew Morton
2005-06-21 15:49 ` Andy Whitcroft
2005-06-21 15:58 ` Andi Kleen
2005-06-21 11:00 ` Bob Picco
2005-06-21 15:57 ` Dave Hansen
2005-06-21 16:45 ` Bob Picco
2005-06-21 14:17 ` Matthew Wilcox
2005-06-21 15:51 ` Andy Whitcroft [this message]
2005-06-21 20:01 ` Andrew Morton
2005-06-21 23:39 ` Dave Hansen
2005-06-22 5:46 ` David S. Miller
2005-06-22 6:00 ` Andrew Morton
2005-07-27 22:42 ` David S. Miller
2005-06-23 22:48 ` Roman Zippel
2005-06-23 22:56 ` Dave Hansen
2005-06-23 23:53 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2005-06-21 15:52 Luck, Tony
2005-06-21 15:58 ` Andy Whitcroft
2005-06-21 16:09 Luck, Tony
2005-06-21 16:17 ` Dave Hansen
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=42B83771.1050304@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=bob.picco@hp.com \
--cc=haveblue@us.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=matthew@wil.cx \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.