From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: linux-next: build failure after merge of the pm tree Date: Thu, 24 May 2018 15:16:51 +0100 Message-ID: <20180524141651.GV4828@sirena.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="YwTTlJgQ7QoYB9ta" Return-path: Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org To: "Rafael J. Wysocki" , Zhang Rui , Wendy Wang , Catalin Marinas , Will Deacon Cc: Linux-Next Mailing List , Linux Kernel Mailing List , linux-arm-kernel@lists.infradead.org List-Id: linux-next.vger.kernel.org --YwTTlJgQ7QoYB9ta Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Rafael, After merging the pm tree, today's linux-next build (arm64 defconfig) failed like this: drivers/acpi/ec.o: In function `acpi_ec_dispatch_gpe': /home/broonie/next/next/drivers/acpi/ec.c:1040: undefined reference to `acpi_dispatch_gpe' /home/broonie/next/next/drivers/acpi/ec.c:1040:(.text+0x228c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `acpi_dispatch_gpe' Probably caused by commit 8f81c457105b5d4 ("ACPI: EC: Dispatch the EC GPE directly on s2idle wake") (though the symbol appears to be there and like it should be built and the relocation warning looks funky...). I've used the PM tree from the last -next. --YwTTlJgQ7QoYB9ta Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlsGyVIACgkQJNaLcl1U h9BPBAf+Lo9wQmffH4H2EV4dSINIApOkXivOXJ7jydPy3Srx6sXD0kbYPZdV/eA3 mPmSaaF631sgU0tgVIwyoP6zpjnY5JIDAEQVoqj/xm+trfnCqzXMa25peTMPR0kR Lt4MDQzua0GqPFh8cQtOAQQcMRboZgcPPymu5JILIILoe1/t6JVxrOjl34KOlFOg WmBJ4abBtcydtHEufjumZ4jzIA0uHSM6raWcEPrOqD7BlHD3PU2NZRJIFY45j+Ns B3NHp+ICvuMTnqSJtDHmvNG3zmV0XSrkW7v/T0VgklyQd48Oq4aZNFW2r6opFb9L pJ9Ap1khBoh/j1xfOAzwEyPqNBsR0Q== =zbJe -----END PGP SIGNATURE----- --YwTTlJgQ7QoYB9ta--