Re: [PATCH v3] memblock: make memblock_find_in_range method private

2021-08-11 Thread Mike Rapoport
On Tue, Aug 10, 2021 at 12:21:46PM -0700, Guenter Roeck wrote: > On 8/10/21 11:55 AM, Mike Rapoport wrote: > > On Mon, Aug 09, 2021 at 12:06:41PM -0700, Guenter Roeck wrote: > > > On Tue, Aug 03, 2021 at 09:42:18AM +0300, Mike Rapoport wrote: > > > > From: Mike Rapoport > > > > > > > > There are

Re: [PATCH v3] memblock: make memblock_find_in_range method private

2021-08-10 Thread Guenter Roeck
On 8/10/21 11:55 AM, Mike Rapoport wrote: On Mon, Aug 09, 2021 at 12:06:41PM -0700, Guenter Roeck wrote: On Tue, Aug 03, 2021 at 09:42:18AM +0300, Mike Rapoport wrote: From: Mike Rapoport There are a lot of uses of memblock_find_in_range() along with memblock_reserve() from the times

Re: [PATCH v3] memblock: make memblock_find_in_range method private

2021-08-10 Thread Mike Rapoport
On Mon, Aug 09, 2021 at 12:06:41PM -0700, Guenter Roeck wrote: > On Tue, Aug 03, 2021 at 09:42:18AM +0300, Mike Rapoport wrote: > > From: Mike Rapoport > > > > There are a lot of uses of memblock_find_in_range() along with > > memblock_reserve() from the times memblock allocation APIs did not

Re: [PATCH v3] memblock: make memblock_find_in_range method private

2021-08-09 Thread Guenter Roeck
On Tue, Aug 03, 2021 at 09:42:18AM +0300, Mike Rapoport wrote: > From: Mike Rapoport > > There are a lot of uses of memblock_find_in_range() along with > memblock_reserve() from the times memblock allocation APIs did not exist. > > memblock_find_in_range() is the very core of memblock

Re: [PATCH v3] memblock: make memblock_find_in_range method private

2021-08-04 Thread Catalin Marinas
On Tue, Aug 03, 2021 at 10:07:37PM +0300, Mike Rapoport wrote: > On Tue, Aug 03, 2021 at 07:05:26PM +0100, Catalin Marinas wrote: > > On Tue, Aug 03, 2021 at 09:42:18AM +0300, Mike Rapoport wrote: > > > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c > > > index 8490ed2917ff..0bffd2d1854f

Re: [PATCH v3] memblock: make memblock_find_in_range method private

2021-08-03 Thread Mike Rapoport
On Tue, Aug 03, 2021 at 07:05:26PM +0100, Catalin Marinas wrote: > On Tue, Aug 03, 2021 at 09:42:18AM +0300, Mike Rapoport wrote: > > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c > > index 8490ed2917ff..0bffd2d1854f 100644 > > --- a/arch/arm64/mm/init.c > > +++ b/arch/arm64/mm/init.c >

Re: [PATCH v3] memblock: make memblock_find_in_range method private

2021-08-03 Thread Catalin Marinas
On Tue, Aug 03, 2021 at 09:42:18AM +0300, Mike Rapoport wrote: > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c > index 8490ed2917ff..0bffd2d1854f 100644 > --- a/arch/arm64/mm/init.c > +++ b/arch/arm64/mm/init.c > @@ -74,6 +74,7 @@ phys_addr_t arm64_dma_phys_limit __ro_after_init; >

[PATCH v3] memblock: make memblock_find_in_range method private

2021-08-03 Thread Mike Rapoport
From: Mike Rapoport There are a lot of uses of memblock_find_in_range() along with memblock_reserve() from the times memblock allocation APIs did not exist. memblock_find_in_range() is the very core of memblock allocations, so any future changes to its internal behaviour would mandate updates