From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Build bot for Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
Date: Fri, 26 Feb 2016 09:49:28 +1100 [thread overview]
Message-ID: <20160226094928.608520d4@canb.auug.org.au> (raw)
In-Reply-To: <E1aYsmb-0006qb-76@optimist>
Hi all,
On Thu, 25 Feb 2016 10:04:29 +0000 Build bot for Mark Brown <broonie@kernel.org> 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
next prev parent reply other threads:[~2016-02-25 22:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 10:04 next-20160225 build: 2 failures 44 warnings (next-20160225) Build bot for Mark Brown
2016-02-25 22:49 ` Stephen Rothwell [this message]
2016-02-26 10:37 ` Kirill A. Shutemov
2016-02-26 3:04 ` Mark Brown
2016-02-26 8:08 ` Thomas Petazzoni
2016-02-26 19:34 ` Bjorn Helgaas
2016-02-26 3:09 ` Mark Brown
[not found] ` <20160226030949.GL18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-26 7:41 ` Guenter Roeck
[not found] ` <56D001BE.2090209-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-02-26 8:21 ` Thomas Petazzoni
2016-02-26 8:14 ` Thomas Petazzoni
[not found] ` <20160226091410.5dad4306-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-02-26 12:12 ` Mark Brown
[not found] ` <20160226121220.GO18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-27 14:40 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160226094928.608520d4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox