diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2019-04-09 15:43:11 +1000 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2019-04-10 14:45:57 +1000 |
| commit | cf7cf6977f531acd5dfe55250d0ee8cbbb6f1ae8 (patch) | |
| tree | 57488b97ebf3c07b2ce5ca005b7296d02b251517 /CREDITS | |
| parent | 7100e8704b61247649c50551b965e71d168df30b (diff) | |
| download | linux-cf7cf6977f531acd5dfe55250d0ee8cbbb6f1ae8.tar.bz2 | |
powerpc/mm: Define MAX_PHYSMEM_BITS for all 64-bit configs
The recent commit 8bc086899816 ("powerpc/mm: Only define
MAX_PHYSMEM_BITS in SPARSEMEM configurations") removed our definition
of MAX_PHYSMEM_BITS when SPARSEMEM is disabled.
This inadvertently broke some 64-bit FLATMEM using configs with eg:
arch/powerpc/include/asm/book3s/64/mmu-hash.h:584:6: error: "MAX_PHYSMEM_BITS" is not defined, evaluates to 0
#if (MAX_PHYSMEM_BITS > MAX_EA_BITS_PER_CONTEXT)
^~~~~~~~~~~~~~~~
Fix it by making sure we define MAX_PHYSMEM_BITS for all 64-bit
configs regardless of SPARSEMEM.
Fixes: 8bc086899816 ("powerpc/mm: Only define MAX_PHYSMEM_BITS in SPARSEMEM configurations")
Reported-by: Andreas Schwab <schwab@linux-m68k.org>
Reported-by: Hugh Dickins <hughd@google.com>
Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions