* Re: Build regressions/improvements in v6.1-rc6 [not found] ` <20221122105054.4062213-1-geert@linux-m68k.org> @ 2022-11-22 10:56 ` Geert Uytterhoeven 2022-11-22 13:55 ` Alex Deucher 0 siblings, 1 reply; 4+ messages in thread From: Geert Uytterhoeven @ 2022-11-22 10:56 UTC (permalink / raw) To: linux-kernel; +Cc: linux-staging, amd-gfx, dri-devel, linux-rdma, linux-um On Tue, 22 Nov 2022, Geert Uytterhoeven wrote: > JFYI, when comparing v6.1-rc6[1] to v6.1-rc5[3], the summaries are: > - build errors: +6/-0 + /kisskb/src/arch/sh/include/asm/io.h: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]: => 239:34 sh4-gcc11/sh-allmodconfig (in cvm_oct_free_hw_memory()) + /kisskb/src/arch/um/include/asm/processor-generic.h: error: called object is not a function or function pointer: => 94:18 + /kisskb/src/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: error: control reaches end of non-void function [-Werror=return-type]: => 1934:1 um-x86_64/um-all{mod,yes}config (in kfd_cpumask_to_apic_id()) + /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'X86_VENDOR_AMD' undeclared (first use in this function): => 149:37 + /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'struct cpuinfo_um' has no member named 'x86_vendor': => 149:22 + /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: control reaches end of non-void function [-Werror=return-type]: => 150:1 um-x86_64/um-allyesconfig > [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/eb7081409f94a9a8608593d0fb63a1aa3d6f95d8/ (all 149 configs) > [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/094226ad94f471a9f19e8f8e7140a09c2625abaa/ (all 149 configs) Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Build regressions/improvements in v6.1-rc6 2022-11-22 10:56 ` Build regressions/improvements in v6.1-rc6 Geert Uytterhoeven @ 2022-11-22 13:55 ` Alex Deucher 2022-11-22 15:00 ` Johannes Berg 0 siblings, 1 reply; 4+ messages in thread From: Alex Deucher @ 2022-11-22 13:55 UTC (permalink / raw) To: Geert Uytterhoeven Cc: linux-kernel, linux-rdma, linux-staging, linux-um, dri-devel, amd-gfx On Tue, Nov 22, 2022 at 5:56 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > On Tue, 22 Nov 2022, Geert Uytterhoeven wrote: > > JFYI, when comparing v6.1-rc6[1] to v6.1-rc5[3], the summaries are: > > - build errors: +6/-0 > > + /kisskb/src/arch/sh/include/asm/io.h: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]: => 239:34 > > sh4-gcc11/sh-allmodconfig (in cvm_oct_free_hw_memory()) > > + /kisskb/src/arch/um/include/asm/processor-generic.h: error: called object is not a function or function pointer: => 94:18 > + /kisskb/src/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: error: control reaches end of non-void function [-Werror=return-type]: => 1934:1 > > um-x86_64/um-all{mod,yes}config (in kfd_cpumask_to_apic_id()) Presumably cpu_data is not defined on um-x86_64? Does it even make sense to build drivers on um-x86_64? Alex > > + /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'X86_VENDOR_AMD' undeclared (first use in this function): => 149:37 > + /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'struct cpuinfo_um' has no member named 'x86_vendor': => 149:22 > + /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: control reaches end of non-void function [-Werror=return-type]: => 150:1 > > um-x86_64/um-allyesconfig > > > [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/eb7081409f94a9a8608593d0fb63a1aa3d6f95d8/ (all 149 configs) > > [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/094226ad94f471a9f19e8f8e7140a09c2625abaa/ (all 149 configs) > > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Build regressions/improvements in v6.1-rc6 2022-11-22 13:55 ` Alex Deucher @ 2022-11-22 15:00 ` Johannes Berg 2022-11-22 16:57 ` Randy Dunlap 0 siblings, 1 reply; 4+ messages in thread From: Johannes Berg @ 2022-11-22 15:00 UTC (permalink / raw) To: Alex Deucher, Geert Uytterhoeven Cc: linux-kernel, linux-rdma, linux-staging, linux-um, dri-devel, amd-gfx On Tue, 2022-11-22 at 08:55 -0500, Alex Deucher wrote: > > > > + /kisskb/src/arch/um/include/asm/processor-generic.h: error: called object is not a function or function pointer: => 94:18 > > + /kisskb/src/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: error: control reaches end of non-void function [-Werror=return-type]: => 1934:1 > > > > um-x86_64/um-all{mod,yes}config (in kfd_cpumask_to_apic_id()) > > Presumably cpu_data is not defined on um-x86_64? Does it even make > sense to build drivers on um-x86_64? Drivers in general yes ;-) This driver, probably not. But the issue is that a lot of drivers "depends on X86_64" or such, where only "X86" is the arch symbol. You could add "X86 && X86_64" to really build on x86 64-bit only. I didn't check this driver, but this has mostly popped up since UM got PCI support some time ago (which I added.) johannes _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Build regressions/improvements in v6.1-rc6 2022-11-22 15:00 ` Johannes Berg @ 2022-11-22 16:57 ` Randy Dunlap 0 siblings, 0 replies; 4+ messages in thread From: Randy Dunlap @ 2022-11-22 16:57 UTC (permalink / raw) To: Johannes Berg, Alex Deucher, Geert Uytterhoeven Cc: linux-kernel, linux-rdma, linux-staging, linux-um, dri-devel, amd-gfx On 11/22/22 07:00, Johannes Berg wrote: > On Tue, 2022-11-22 at 08:55 -0500, Alex Deucher wrote: >>> >>> + /kisskb/src/arch/um/include/asm/processor-generic.h: error: called object is not a function or function pointer: => 94:18 >>> + /kisskb/src/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: error: control reaches end of non-void function [-Werror=return-type]: => 1934:1 >>> >>> um-x86_64/um-all{mod,yes}config (in kfd_cpumask_to_apic_id()) >> >> Presumably cpu_data is not defined on um-x86_64? Does it even make >> sense to build drivers on um-x86_64? > > Drivers in general yes ;-) > > This driver, probably not. > > But the issue is that a lot of drivers "depends on X86_64" or such, > where only "X86" is the arch symbol. You could add "X86 && X86_64" to > really build on x86 64-bit only. > > I didn't check this driver, but this has mostly popped up since UM got > PCI support some time ago (which I added.) I have patches for lots of these issues, but some people said that they would want to build DRM drivers for use with KUNIT (i.e. UML), so I thought that meant my patches were not needed. -- ~Randy _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-11-22 16:57 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <CAHk-=wjKJyzfJmOzBdEOqCFRc8Fh-rdGM4tvMXfW0WXbbHwV0w@mail.gmail.com> [not found] ` <20221122105054.4062213-1-geert@linux-m68k.org> 2022-11-22 10:56 ` Build regressions/improvements in v6.1-rc6 Geert Uytterhoeven 2022-11-22 13:55 ` Alex Deucher 2022-11-22 15:00 ` Johannes Berg 2022-11-22 16:57 ` Randy Dunlap
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).