From: Johannes Berg <johannes@sipsolutions.net>
To: Alex Deucher <alexdeucher@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-staging@lists.linux.dev, linux-um@lists.infradead.org,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: Build regressions/improvements in v6.1-rc6
Date: Tue, 22 Nov 2022 16:00:34 +0100 [thread overview]
Message-ID: <021efb6c9295402cf05406bb319c441c0b0229b3.camel@sipsolutions.net> (raw)
In-Reply-To: <CADnq5_PvouSKugXxJXqkVeZf+kbP8+hhUKFgVALSO=MOW3jzvA@mail.gmail.com>
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
next prev parent reply other threads:[~2022-11-22 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2022-11-22 16:57 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=021efb6c9295402cf05406bb319c441c0b0229b3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-um@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).