All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
	davem@davemloft.net, shangw@linux.vnet.ibm.com, tj@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 046/181] mm: remove sparsemem allocation details from the bootmem allocator
Date: Tue, 26 Jun 2012 21:08:25 +0200	[thread overview]
Message-ID: <20120626190825.GF27816@cmpxchg.org> (raw)
In-Reply-To: <CAE9FiQWVEDHKeRN3+t39Hch8wpNdjsv15yTyVVLGRdK=yw2n4g@mail.gmail.com>

On Tue, Jun 26, 2012 at 11:20:16AM -0700, Yinghai Lu wrote:
> On Tue, Jun 26, 2012 at 1:17 AM, Johannes Weiner <hannes@cmpxchg.org> wrote:
> > No use in reverting it, as the bootmem version was already broken
> > before, when the limit was removed in f5bf18f "bootmem/sparsemem:
> > remove limit constraint in alloc_bootmem_section".
> >
> > I'm okay with exporting and using ___alloc_bootmem_node_nopanic() in
> > 3.5.
> 
> Good. Assume that is Acked-by you.

Yes,

Acked-by: Johannes Weiner <hannes@cmpxchg.org>

Thanks, Yinghai!

      reply	other threads:[~2012-06-26 19:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120529220636.AAA66A0308@akpm.mtv.corp.google.com>
     [not found] ` <CAE9FiQVEq5j1zoKS31fgfG_3xZSyfqsjdDorDku-Sgj6BTShEg@mail.gmail.com>
2012-06-23  2:05   ` [patch 046/181] mm: remove sparsemem allocation details from the bootmem allocator Yinghai Lu
2012-06-23  9:17     ` Johannes Weiner
2012-06-23 18:58       ` Yinghai Lu
2012-06-23 22:06         ` Johannes Weiner
2012-06-23 22:35           ` Yinghai Lu
2012-06-26  8:17             ` Johannes Weiner
2012-06-26 18:20               ` Yinghai Lu
2012-06-26 19:08                 ` Johannes Weiner [this message]

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=20120626190825.GF27816@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shangw@linux.vnet.ibm.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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 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.