[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1910221703540.25457@viisi.sifive.com>
Date: Tue, 22 Oct 2019 17:04:24 -0700 (PDT)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: David Abdurachmanov <david.abdurachmanov@...il.com>
cc: Palmer Dabbelt <palmer@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>,
Anup Patel <Anup.Patel@....com>,
Mike Rapoport <rppt@...ux.ibm.com>,
Greentime Hu <greentime.hu@...ive.com>,
Stefan O'Rear <sorear2@...il.com>,
David Abdurachmanov <david.abdurachmanov@...ive.com>,
Alexandre Ghiti <alex@...ti.fr>,
Logan Gunthorpe <logang@...tatee.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: fix fs/proc/kcore.c compilation with sparsemem
enabled
On Tue, 22 Oct 2019, David Abdurachmanov wrote:
> 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@...ive.com>
> Tested-by: David Abdurachmanov <david.abdurachmanov@...ive.com>
Thanks, queued for v5.4-rc with Logan's Reviewed-by:.
- Paul
Powered by blists - more mailing lists