[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <021efb6c9295402cf05406bb319c441c0b0229b3.camel@sipsolutions.net>
Date: Tue, 22 Nov 2022 16:00:34 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Alex Deucher <alexdeucher@...il.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-staging@...ts.linux.dev, linux-um@...ts.infradead.org,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org
Subject: Re: Build regressions/improvements in v6.1-rc6
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
Powered by blists - more mailing lists