diff options
| author | Rob Herring <robh@kernel.org> | 2018-03-09 09:54:07 -0600 |
|---|---|---|
| committer | Michal Simek <michal.simek@xilinx.com> | 2018-03-16 12:51:27 +0100 |
| commit | 101646a24a2f9cdb61d7732459fbf068a7bbb542 (patch) | |
| tree | 679febdfa59103d83488dba3adabb41312b3bd64 /mm | |
| parent | cd4dfee6a8bfbbe404e9905aff85e267ec99f5fa (diff) | |
| download | op-kernel-dev-101646a24a2f9cdb61d7732459fbf068a7bbb542.zip op-kernel-dev-101646a24a2f9cdb61d7732459fbf068a7bbb542.tar.gz | |
microblaze: switch to NO_BOOTMEM
Microblaze doesn't set CONFIG_NO_BOOTMEM and so memblock_virt_alloc()
doesn't work for CONFIG_HAVE_MEMBLOCK && !CONFIG_NO_BOOTMEM.
Similar change was already done by others architectures
"ARM: mm: Remove bootmem code and switch to NO_BOOTMEM"
(sha1: 84f452b1e8fc73ac0e31254c66e3e2260ce5263d)
or
"openrisc: Consolidate setup to use memblock instead of bootmem"
(sha1: 266c7fad157265bb54d17db1c9545f2aaa488643)
or
"parisc: Drop bootmem and switch to memblock"
(sha1: 4fe9e1d957e45ad8eba9885ee860a0e93d13a7c7)
or
"powerpc: Remove bootmem allocator"
(sha1: 10239733ee8617bac3f1c1769af43a88ed979324)
or
"s390/mm: Convert bootmem to memblock"
(sha1: 50be634507284eea38df78154d22615d21200b42)
or
"sparc64: Convert over to NO_BOOTMEM."
(sha1: 625d693e9784f988371e69c2b41a2172c0be6c11)
or
"xtensa: drop sysmem and switch to memblock"
(sha1: 0e46c1115f5816949220d62dd3ff04aa68e7ac6b)
Issue was introduced by:
"of/fdt: use memblock_virt_alloc for early alloc"
(sha1: 0fa1c579349fdd90173381712ad78aa99c09d38b)
Signed-off-by: Rob Herring <robh@kernel.org>
Tested-by: Alvaro Gamez Machado <alvaro.gamez@hazent.com>
Tested-by: Michal Simek <michal.simek@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions
