From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
Yinghai Lu <yhlu.kernel.send@gmail.com>,
linuxppc-dev@ozlabs.org, Badari Pulavarty <pbadari@us.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH] mm: allocate usemap at first instead of mem_map in sparse_init
Date: Wed, 2 Apr 2008 18:43:24 -0700 [thread overview]
Message-ID: <86802c440804021843i57f5e82fsee5121bf97d65909@mail.gmail.com> (raw)
In-Reply-To: <86802c440804021744m7c6e3d94vcb6af3ebcaa71b5b@mail.gmail.com>
On Wed, Apr 2, 2008 at 5:44 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>
> On Wed, Apr 2, 2008 at 3:52 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Wed, 2 Apr 2008 15:25:48 -0700 Yinghai Lu <yhlu.kernel.send@gmail.com> wrote:
> >
> > > [PATCH] mm: allocate usemap at first instead of mem_map in sparse_init
> > >
> > > on powerpc,
> > >
> > > On Wed, Apr 2, 2008 at 12:22 PM, Badari Pulavarty <pbadari@us.ibm.com> wrote:
> > > >
> > > > On Wed, 2008-04-02 at 18:17 +1100, Michael Ellerman wrote:
> > > > > On Wed, 2008-04-02 at 12:38 +0530, Kamalesh Babulal wrote:
> > > > > > Andrew Morton wrote:
> > > > > > > On Wed, 02 Apr 2008 11:55:36 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> > > so try to allocate usemap at first altogether.
> >
> > I have to turn all the above crud into a proper changelog. I'd prefer that
> > you do it.
> >
> > Unless this patch should be folded into another one, in which case it
> > doesn't matter.
> >
> >
> > > Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
> > >
> > > diff --git a/mm/sparse.c b/mm/sparse.c
> > > index d3cb085..782ebe5 100644
> > > --- a/mm/sparse.c
> > > +++ b/mm/sparse.c
> >
> > We shouldn't merge this patch on its own because then that will leave a
> > non-bisectable region in the powerpc history.
> >
> > So which patch is this patch fixing? Lexically it applies to
> > mm-allocate-section_map-for-sparse_init.patch (and its updates). But is
> > that where it logically lies?
>
> yes. we should fold
>
>
> mm-make-mem_map-allocation-continuous.patch
>
> mm-allocate-section_map-for-sparse_init.patch
> and this one
>
please check the big one.
http://lkml.org/lkml/2008/4/2/650
YH
next prev parent reply other threads:[~2008-04-03 1:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 22:25 [PATCH] mm: allocate usemap at first instead of mem_map in sparse_init Yinghai Lu
2008-04-02 22:52 ` Andrew Morton
2008-04-03 0:44 ` Yinghai Lu
2008-04-03 1:30 ` [PATCH] mm: make mem_map allocation continuous v2 Yinghai Lu
2008-04-03 2:22 ` Andrew Morton
2008-04-03 4:16 ` Yinghai Lu
2008-04-03 10:49 ` Kamalesh Babulal
2008-04-03 3:22 ` Yasunori Goto
2008-04-03 1:43 ` Yinghai Lu [this message]
2008-04-02 23:51 ` [PATCH] mm: allocate usemap at first instead of mem_map in sparse_init Badari Pulavarty
2008-04-03 0:47 ` Yinghai Lu
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=86802c440804021843i57f5e82fsee5121bf97d65909@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=pbadari@us.ibm.com \
--cc=yhlu.kernel.send@gmail.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;
as well as URLs for NNTP newsgroup(s).