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 May 2020 11:43:38 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Andrew Morton <akpm@linux-foundation.org>
Cc:     Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Ira Weiny <ira.weiny@intel.com>
Subject: Re: linux-next: build failure after merge of the akpm-current tree
Message-ID: <20200508114338.02d2b843@canb.auug.org.au>
In-Reply-To: <20200507221721.0330271c@canb.auug.org.au>
References: <20200507221721.0330271c@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/gWV6hIMcFCsa=dV2OB6P/I.";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--Sig_/gWV6hIMcFCsa=dV2OB6P/I.
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

On Thu, 7 May 2020 22:17:21 +1000 Stephen Rothwell <sfr@canb.auug.org.au> w=
rote:
>
> After merging the akpm-current tree, today's linux-next build (arm
> collie_defconfig and many others) failed like this:
>=20
> arch/arm/mm/dma-mapping.c: In function 'dma_cache_maint_page':
> arch/arm/mm/dma-mapping.c:892:6: error: implicit declaration of function =
'kunmap_high' [-Werror=3Dimplicit-function-declaration]
>       kunmap_high(page);
>       ^
> arch/arm/mm/flush.c: In function '__flush_dcache_page':
> arch/arm/mm/flush.c:221:6: error: implicit declaration of function 'kunma=
p_high' [-Werror=3Dimplicit-function-declaration]
>       kunmap_high(page + i);
>       ^
>=20
> Caused by commit
>=20
>   6b66ab470b4d ("arch/kunmap: remove duplicate kunmap implementations")
>=20
> kunmap_high() is now only declared when CONFIG_HIGHMEM is defined.

Is there anything that can be done quickly about this as it broke a
large number of builds ...

--=20
Cheers,
Stephen Rothwell

--Sig_/gWV6hIMcFCsa=dV2OB6P/I.
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl60uUoACgkQAVBC80lX
0GyOuAgAkfoqA2UzIk5jra5cPLhHMe8/Ug0E3/DxEX/uFHLBQ9wRytAT8SM1Ty0O
ssm13c5YtZOHfOeWFvyh746gw9QcXB8ORUdeeW1/bbtoFRwq/kptP0RRP9mHz+RA
rAHaT/DDYsHB+JRKkjyJYk4Y4uy4L+9B0wBA6wRlIqs+c6PPPom9gbayk+kD0nLd
I3bVjDPCYbov5w1y1K0pzXCalg2XNsaKEHT8Zqtf7QA4eoNTGQX/2unOdTMAFWrJ
bfjnnIoNzzReNB+w0dYD5XOE0Tf1CiwUsjZ8kVR0Jla9cwmBst/liRylTkV1QtV+
dDMn35nM00Tz09aVVCWKnTNxbiPEvA==
=P9ww
-----END PGP SIGNATURE-----

--Sig_/gWV6hIMcFCsa=dV2OB6P/I.--