Re: [PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM

So, since there haven't been any new comments for over a week, I'll be collecting the patchset v2 tomorrow. Regards, -Sergey On Thu, Jan 18, 2018 at 01:22:58AM +0300, Serge Semin wrote: > Even though it's common to see the architecture code using both > bootmem and memblock early memory allocat

Re: [PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM

Hello Alexander, On Thu, Jan 25, 2018 at 06:58:07PM +0100, Alexander Sverdlin wrote: > Hello Serge, > > On 17/01/18 23:22, Serge Semin wrote: > > The patchset is applied on top of kernel 4.15-rc8 and can be found > > submitted at my repo: > > https://github.com/fancer/Linux-kernel-MIPS-memblock

Re: [PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM

Hello Serge, On 17/01/18 23:22, Serge Semin wrote: > The patchset is applied on top of kernel 4.15-rc8 and can be found > submitted at my repo: > https://github.com/fancer/Linux-kernel-MIPS-memblock-project I've tested the Linux from your repo on Octeon2 and it looks good to me. I've only tested

Re: [PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM

Hi Mathieu, On 23/01/18 11:29, Mathieu Malaterre wrote: Hi Matt, On Mon, Jan 22, 2018 at 5:36 PM, Matt Redfearn wrote: Hi Serge, On 17/01/18 22:22, Serge Semin wrote: Even though it's common to see the architecture code using both bootmem and memblock early memory allocators, it's not go

Re: [PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM

Hi Matt, On Mon, Jan 22, 2018 at 5:36 PM, Matt Redfearn wrote: > > Hi Serge, > > > On 17/01/18 22:22, Serge Semin wrote: >> >> Even though it's common to see the architecture code using both >> bootmem and memblock early memory allocators, it's not good for >> multiple reasons. First of all, it's

Re: [PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM

On Mon, Jan 22, 2018 at 04:36:40PM +, Matt Redfearn wrote: Hello Matt, > Hi Serge, > > On 17/01/18 22:22, Serge Semin wrote: > >Even though it's common to see the architecture code using both > >bootmem and memblock early memory allocators, it's not good for > >multiple reasons. First of a

Re: [PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM

Hi Serge, On 17/01/18 22:22, Serge Semin wrote: Even though it's common to see the architecture code using both bootmem and memblock early memory allocators, it's not good for multiple reasons. First of all, it's redundant to have two early memory allocator while one would be more than enough fr

[PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM

Even though it's common to see the architecture code using both bootmem and memblock early memory allocators, it's not good for multiple reasons. First of all, it's redundant to have two early memory allocator while one would be more than enough from functionality and stability points of view. Seco