* OK to merge via powerpc? (was Re: [PATCH 05/14] mm: make memblock_alloc_base_nid non-static) [not found] ` <20180213150824.27689-6-npiggin@gmail.com> @ 2018-03-13 12:06 ` Michael Ellerman 2018-03-13 19:41 ` Andrew Morton 0 siblings, 1 reply; 3+ messages in thread From: Michael Ellerman @ 2018-03-13 12:06 UTC (permalink / raw) To: akpm, mhocko, catalin.marinas, pasha.tatashin, takahiro.akashi, gi-oh.kim, npiggin, baiyaowei, bob.picco, ard.biesheuvel, linux-mm, linux-kernel Cc: linuxppc-dev Anyone object to us merging the following patch via the powerpc tree? Full series is here if anyone's interested: http://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=28377&state=* cheers Nicholas Piggin <npiggin@gmail.com> writes: > This will be used by powerpc to allocate per-cpu stacks and other > data structures node-local where possible. > > Signed-off-by: Nicholas Piggin <npiggin@gmail.com> > --- > include/linux/memblock.h | 5 ++++- > mm/memblock.c | 2 +- > 2 files changed, 5 insertions(+), 2 deletions(-) > > diff --git a/include/linux/memblock.h b/include/linux/memblock.h > index 8be5077efb5f..8cab51398705 100644 > --- a/include/linux/memblock.h > +++ b/include/linux/memblock.h > @@ -316,9 +316,12 @@ static inline bool memblock_bottom_up(void) > #define MEMBLOCK_ALLOC_ANYWHERE (~(phys_addr_t)0) > #define MEMBLOCK_ALLOC_ACCESSIBLE 0 > > -phys_addr_t __init memblock_alloc_range(phys_addr_t size, phys_addr_t align, > +phys_addr_t memblock_alloc_range(phys_addr_t size, phys_addr_t align, > phys_addr_t start, phys_addr_t end, > ulong flags); > +phys_addr_t memblock_alloc_base_nid(phys_addr_t size, > + phys_addr_t align, phys_addr_t max_addr, > + int nid, ulong flags); > phys_addr_t memblock_alloc_base(phys_addr_t size, phys_addr_t align, > phys_addr_t max_addr); > phys_addr_t __memblock_alloc_base(phys_addr_t size, phys_addr_t align, > diff --git a/mm/memblock.c b/mm/memblock.c > index 5a9ca2a1751b..cea2af494da0 100644 > --- a/mm/memblock.c > +++ b/mm/memblock.c > @@ -1190,7 +1190,7 @@ phys_addr_t __init memblock_alloc_range(phys_addr_t size, phys_addr_t align, > flags); > } > > -static phys_addr_t __init memblock_alloc_base_nid(phys_addr_t size, > +phys_addr_t __init memblock_alloc_base_nid(phys_addr_t size, > phys_addr_t align, phys_addr_t max_addr, > int nid, ulong flags) > { > -- > 2.16.1 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: OK to merge via powerpc? (was Re: [PATCH 05/14] mm: make memblock_alloc_base_nid non-static) 2018-03-13 12:06 ` OK to merge via powerpc? (was Re: [PATCH 05/14] mm: make memblock_alloc_base_nid non-static) Michael Ellerman @ 2018-03-13 19:41 ` Andrew Morton 2018-03-14 0:56 ` Nicholas Piggin 0 siblings, 1 reply; 3+ messages in thread From: Andrew Morton @ 2018-03-13 19:41 UTC (permalink / raw) To: Michael Ellerman Cc: mhocko, catalin.marinas, pasha.tatashin, takahiro.akashi, gi-oh.kim, npiggin, baiyaowei, bob.picco, ard.biesheuvel, linux-mm, linux-kernel, linuxppc-dev On Tue, 13 Mar 2018 23:06:35 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote: > Anyone object to us merging the following patch via the powerpc tree? > > Full series is here if anyone's interested: > http://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=28377&state=* > Yup, please go ahead. I assume the change to the memblock_alloc_range() declaration was an unrelated, unchangelogged cleanup. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: OK to merge via powerpc? (was Re: [PATCH 05/14] mm: make memblock_alloc_base_nid non-static) 2018-03-13 19:41 ` Andrew Morton @ 2018-03-14 0:56 ` Nicholas Piggin 0 siblings, 0 replies; 3+ messages in thread From: Nicholas Piggin @ 2018-03-14 0:56 UTC (permalink / raw) To: Andrew Morton Cc: Michael Ellerman, mhocko, catalin.marinas, pasha.tatashin, takahiro.akashi, gi-oh.kim, baiyaowei, bob.picco, ard.biesheuvel, linux-mm, linux-kernel, linuxppc-dev On Tue, 13 Mar 2018 12:41:28 -0700 Andrew Morton <akpm@linux-foundation.org> wrote: > On Tue, 13 Mar 2018 23:06:35 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote: > > > Anyone object to us merging the following patch via the powerpc tree? > > > > Full series is here if anyone's interested: > > http://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=28377&state=* > > > > Yup, please go ahead. > > I assume the change to the memblock_alloc_range() declaration was an > unrelated, unchangelogged cleanup. > It is. I'm trying to get better at that. Michael might drop that bit if he's not already sick of fixing up my patches... Thanks, Nick ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-03-14 0:56 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <20180213150824.27689-1-npiggin@gmail.com> [not found] ` <20180213150824.27689-6-npiggin@gmail.com> 2018-03-13 12:06 ` OK to merge via powerpc? (was Re: [PATCH 05/14] mm: make memblock_alloc_base_nid non-static) Michael Ellerman 2018-03-13 19:41 ` Andrew Morton 2018-03-14 0:56 ` Nicholas Piggin
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).