summaryrefslogtreecommitdiff
path: root/arch/riscv/Kconfig.debug
diff options
context:
space:
mode:
authorDavid Abdurachmanov <david.abdurachmanov@gmail.com>2019-10-22 19:21:35 +0300
committerPaul Walmsley <paul.walmsley@sifive.com>2019-10-24 00:53:46 +0300
commit90db7b220c9aea91948e82d51b99514f9398f9b5 (patch)
tree82d19461ad5c0371778a75f4c722cf8aac27a336 /arch/riscv/Kconfig.debug
parent7d194c2100ad2a6dded545887d02754948ca5241 (diff)
downloadlinux-90db7b220c9aea91948e82d51b99514f9398f9b5.tar.xz
riscv: fix fs/proc/kcore.c compilation with sparsemem enabled
Failed to compile Fedora/RISCV kernel (5.4-rc3+) with sparsemem enabled: fs/proc/kcore.c: In function 'read_kcore': fs/proc/kcore.c:510:8: error: implicit declaration of function 'kern_addr_valid'; did you mean 'virt_addr_valid'? [-Werror=implicit-function-declaration] 510 | if (kern_addr_valid(start)) { | ^~~~~~~~~~~~~~~ | virt_addr_valid Looking at other architectures I don't see kern_addr_valid being guarded by CONFIG_FLATMEM. Fixes: d95f1a542c3d ("RISC-V: Implement sparsemem") Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com> Tested-by: David Abdurachmanov <david.abdurachmanov@sifive.com> Reviewed-by: Logan Gunthorpe <logang@deltatee.com> Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
Diffstat (limited to 'arch/riscv/Kconfig.debug')
0 files changed, 0 insertions, 0 deletions