Hi Conor, On Tue, May 09, 2023 at 06:50:07PM +0100, Conor Dooley wrote: > Hey Sunil, > > On Mon, May 08, 2023 at 05:22:24PM +0530, Sunil V L wrote: > > RINTC structures in the MADT provide mapping between the hartid > > and the CPU. This is required many times even at run time like > > cpuinfo. So, instead of parsing the ACPI table every time, cache > > the RINTC structures and provide a function to get the correct > > RINTC structure for a given cpu. > > > > Signed-off-by: Sunil V L <sunilvl@xxxxxxxxxxxxxxxx> > > Acked-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> > > From this patch until "RISC-V: Add ACPI initialization in > setup_arch()" (which is 19/21), the series fails to build. > > allmodconfig, clang-16: > ../arch/riscv/include/asm/acpi.h:22:23: error: unknown type name 'acpi_physical_address'; did you mean 'efi_physical_addr_t'? > ../arch/riscv/include/asm/acpi.h:22:51: error: unknown type name 'acpi_size' > > rv32_defconfig, clang-16: > arch/riscv/kernel/setup.c:297:7: error: use of undeclared identifier 'acpi_disabled'; did you mean '__cpu_disable'? > arch/riscv/kernel/setup.c:297:7: warning: address of function '__cpu_disable' will always evaluate to 'true' [-Wpointer-bool-conversion] > > I ballsed up a toolchain upgrade to gcc-13, so the whole series is > showing build issues on patchwork for the gcc configurations: > https://patchwork.kernel.org/project/linux-riscv/list/?series=745787 > > However, I suspect that the same patches that fail for clang-16 will > fail for gcc-13 too, once I have fixed that! > My bad. It is a commit order issue. Let me fix it. Thanks! Sunil
