From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: next-20160225 build: 2 failures 44 warnings (next-20160225) Date: Fri, 26 Feb 2016 09:49:28 +1100 Message-ID: <20160226094928.608520d4@canb.auug.org.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from ozlabs.org ([103.22.144.67]:48339 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750850AbcBYWta (ORCPT ); Thu, 25 Feb 2016 17:49:30 -0500 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Build bot for Mark Brown Cc: kernel-build-reports@lists.linaro.org, linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org, Andrew Morton , "Kirill A. Shutemov" Hi all, On Thu, 25 Feb 2016 10:04:29 +0000 Build bot for Mark Brown wrote: > > arm64-allmodconfig > ../arch/arm64/mm/hugetlbpage.c:127:42: error: macro "pte_alloc_map" passed 4 arguments, but takes just 3 > ../arch/arm64/mm/hugetlbpage.c:127:9: error: 'pte_alloc_map' undeclared (first use in this function) Caused by an interaction between commit b9c9252f278d ("mm: cleanup *pte_alloc* interfaces") from the akpm-current tree and commit 66b3923a1a0f ("arm64: hugetlb: add support for PTE contiguous bit") from Linus' tree (added before v4.5-rc1). I will add a fix patch today that removes the second argument from the new pte_alloc_map() call added by the latter commit. Again, grep is your friend ... (yes, I realise that the akpm-current tree patch was probably written against v4.4 (or some such)). -- Cheers, Stephen Rothwell