Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 8 Oct 2021 19:29:10 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Simon Ser <contact@emersion.fr>
Cc:     Alex Deucher <alexdeucher@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the amdgpu tree
Message-ID: <20211008192910.600a188d@canb.auug.org.au>
In-Reply-To: <jXLIcCYkgHdIQna5SW6W4GGHVG5By4-GXiaosbXyyaYXFNTH60nmH6twdxMYgM2X63FhEOyxU7Qh_vbKFywBKmUwp7l4DYXe_hTt86AS-ZM=@emersion.fr>
References: <20211008113116.4bdd7b6c@canb.auug.org.au>
        <jXLIcCYkgHdIQna5SW6W4GGHVG5By4-GXiaosbXyyaYXFNTH60nmH6twdxMYgM2X63FhEOyxU7Qh_vbKFywBKmUwp7l4DYXe_hTt86AS-ZM=@emersion.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/CRuPf2hkRrq=FJoYpdb7XO7";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/CRuPf2hkRrq=FJoYpdb7XO7
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Simon,

On Fri, 08 Oct 2021 06:27:05 +0000 Simon Ser <contact@emersion.fr> wrote:
>
> On Friday, October 8th, 2021 at 02:31, Stephen Rothwell <sfr@canb.auug.or=
g.au> wrote:
>=20
> > 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 C=
RTC on ChromeOS")
> >
> > I have used the amdgpu tree from next-20211007 for today. =20
>=20
> Not sure why this would happen. This commit builds fine on my machine, an=
d I
> don't think it's possible to disable this function with Kconfig?

That symbol (get_mm_exe_file) is not exported to modules.

--=20
Cheers,
Stephen Rothwell

--Sig_/CRuPf2hkRrq=FJoYpdb7XO7
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmFgAVYACgkQAVBC80lX
0GyFfwf7BalbHntmA7QkynH0M1UpodMwHzD6wIQcEKgU/8JdNQv4AH4ExwObw5tb
71+R3p0kBr1OBFDXdxNNSBSBZCUZRE4hQBnBVjm8NMO1eFMGehSRdMa0rcTNbPIR
tCvYozHDNs94J1oL3jzzM3lAGHImhINmVbRoBsLUlHZyoVANLa26uxyBzO+JZxd3
0wRZcEVrwP7OGWYMseuX9ni5EmXMcJkwzpCevV0F/644ZoBf5wV6b07MheAzA55Z
nMVVffj72mILqig73RwuwRr/M6FDqMWW9vYlIfeeAhypqnIY1d6UowKkkGVRmt4b
qBoDq3jPhFoOJNoUwcqBbPEHHO7sJQ==
=/IkY
-----END PGP SIGNATURE-----

--Sig_/CRuPf2hkRrq=FJoYpdb7XO7--