Thread (4 messages) 4 messages, 2 authors, 2020-08-30

Re: [ALTERNATE PATCH] memblock: fix min_low_pfn/max_low_pfn build errors

From: Mike Rapoport <hidden>
Date: 2020-08-30 09:57:11
Also in: lkml

Hi Randy,

On Sat, Aug 29, 2020 at 08:40:51AM -0700, Randy Dunlap wrote:
On 8/29/20 6:04 AM, Mike Rapoport wrote:
quoted
On Fri, Aug 28, 2020 at 05:01:39PM -0700, Randy Dunlap wrote:
quoted
Export min_low_pfn & max_low_pfn in mm/memblock.c to fix build errors
on arch/microblaze/ and arch/ia64/: (e.g.)
Please don't. This would give driver developers a wrong impression that
these variables can be used to query memory boundaries, but this is not
the case, at least not on all architectures.

I would prefer fixing it up locally for microblaze and ia64.
I did that.
and that's why this is labeled as an ALTERNATE PATCH.
I've seen that, I just wanted to make sure that Andrew wouldn't pick
this one :)

I can help with taking microblaze and ia64 patches via memblock tree
once we have Acks from the arch maintainers.
 
thanks.
-- 
~Randy
-- 
Sincerely yours,
Mike.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help