From: Emil Medve <Emilian.Medve@Freescale.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH 1/5] powerpc: Remove bootmem allocator
Date: Thu, 30 Oct 2014 22:35:50 -0500 [thread overview]
Message-ID: <54530396.1020306@Freescale.com> (raw)
In-Reply-To: <1414721739.21815.4.camel@concordia>
Hello Michael,
On 10/30/2014 09:15 PM, Michael Ellerman wrote:
> On Thu, 2014-10-30 at 01:00 -0500, Emil Medve wrote:
>> On 09/17/2014 07:15 AM, Anton Blanchard wrote:
>>> At the moment we transition from the memblock alloctor to the bootmem
>>> allocator. Gitting rid of the bootmem allocator removes a bunch of
>>> complicated code (most of which I owe the dubious honour of being
>>> responsible for writing).
>>
>> Any idea on how to move these patches forward?
>
> It's in my test branch and will go into next on Monday.
Thank you
Cheers,
next prev parent reply other threads:[~2014-10-31 3:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 12:15 [PATCH 1/5] powerpc: Remove bootmem allocator Anton Blanchard
2014-09-17 12:15 ` [PATCH 2/5] powerpc: Remove some old bootmem related comments Anton Blanchard
2014-09-17 12:15 ` [PATCH 3/5] powerpc: Remove superfluous bootmem includes Anton Blanchard
2014-09-17 12:15 ` [PATCH 4/5] powerpc: Move sparse_init() into initmem_init Anton Blanchard
2014-09-17 12:15 ` [PATCH 5/5] powerpc: make __ffs return unsigned long Anton Blanchard
2014-10-30 6:00 ` [PATCH 1/5] powerpc: Remove bootmem allocator Emil Medve
2014-10-31 2:15 ` Michael Ellerman
2014-10-31 3:35 ` Emil Medve [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-17 5:58 Anton Blanchard
2014-08-05 6:32 Anton Blanchard
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=54530396.1020306@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).