[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <jXLIcCYkgHdIQna5SW6W4GGHVG5By4-GXiaosbXyyaYXFNTH60nmH6twdxMYgM2X63FhEOyxU7Qh_vbKFywBKmUwp7l4DYXe_hTt86AS-ZM=@emersion.fr>
Date: Fri, 08 Oct 2021 06:27:05 +0000
From: Simon Ser <contact@...rsion.fr>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Alex Deucher <alexdeucher@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the amdgpu tree
On Friday, October 8th, 2021 at 02:31, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> After merging the amdgpu tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: "get_mm_exe_file" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>
> Caused by commit
>
> f4f80155e6e8 ("amd/display: only require overlay plane to cover whole CRTC on ChromeOS")
>
> I have used the amdgpu tree from next-20211007 for today.
Not sure why this would happen. This commit builds fine on my machine, and I
don't think it's possible to disable this function with Kconfig?
Powered by blists - more mailing lists