From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Sudeep Holla <sudeep.holla@arm.com>
Cc: Build bot for Mark Brown <broonie@kernel.org>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
Date: Fri, 26 Feb 2016 13:37:51 +0300 [thread overview]
Message-ID: <20160226103751.GA86588@black.fi.intel.com> (raw)
In-Reply-To: <20160226094928.608520d4@canb.auug.org.au>
On Fri, Feb 26, 2016 at 09:49:28AM +1100, Stephen Rothwell wrote:
> 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.
Sudeep Holla has posted patch for this.
http://lkml.kernel.org/r/1456414385-13775-1-git-send-email-sudeep.holla@arm.com
>
> 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
--
Kirill A. Shutemov
next prev parent reply other threads:[~2016-02-26 10:37 UTC|newest]
Thread overview: 27+ 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
2016-02-26 10:37 ` Kirill A. Shutemov [this message]
2016-02-26 3:04 ` Mark Brown
2016-02-26 3:04 ` Mark Brown
2016-02-26 8:08 ` Thomas Petazzoni
2016-02-26 8:08 ` Thomas Petazzoni
2016-02-26 19:34 ` Bjorn Helgaas
2016-02-26 19:34 ` Bjorn Helgaas
2016-02-26 3:09 ` Mark Brown
2016-02-26 3:09 ` Mark Brown
2016-02-26 3:09 ` Mark Brown
[not found] ` <20160226030949.GL18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-26 7:41 ` Guenter Roeck
2016-02-26 7:41 ` Guenter Roeck
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:21 ` Thomas Petazzoni
2016-02-26 8:21 ` Thomas Petazzoni
2016-02-26 8:14 ` Thomas Petazzoni
2016-02-26 8:14 ` 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
2016-02-26 12:12 ` Mark Brown
2016-02-26 12:12 ` Mark Brown
[not found] ` <20160226121220.GO18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-27 14:40 ` Thomas Petazzoni
2016-02-27 14:40 ` Thomas Petazzoni
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=20160226103751.GA86588@black.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sudeep.holla@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.