From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Hillf Danton <hillf.zj@alibaba-inc.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: next-20170202 build: 4 failures 7 warnings (next-20170202)
Date: Fri, 3 Feb 2017 18:44:42 +0200 [thread overview]
Message-ID: <20170203164442.GA3183@rapoport-lnx> (raw)
In-Reply-To: <20170203120123.ep5ceio5gzbnismn@sirena.org.uk>
On Fri, Feb 03, 2017 at 01:01:23PM +0100, Mark Brown wrote:
> On Thu, Feb 02, 2017 at 06:08:44PM -0500, Paul Gortmaker wrote:
> > On Thu, Feb 2, 2017 at 5:23 AM, Build bot for Mark Brown
>
> > > arm-allnoconfig
> > > ../mm/nommu.c:1201:15: error: conflicting types for 'do_mmap'
> > > ../mm/nommu.c:1580:5: error: conflicting types for 'do_munmap'
>
> > Also in sfr build: http://kisskb.ellerman.id.au/kisskb/buildresult/12924855/
>
> > Bisects as follows:
>
> > 5b8d82e2e798609e113ec0dae37708f0578b68e2 is the first bad commit
> > commit 5b8d82e2e798609e113ec0dae37708f0578b68e2
> > Author: Mike Rapoport <rppt@linux.vnet.ibm.com>
> > Date: Thu Feb 2 10:46:41 2017 +1100
> >
> > userfaultfd: non-cooperative: add event for memory unmaps
>
> I'm seeing that showing up as 197b090832eaa4a6e in -next, adding the
> other people who acked/signed off on the commit.
Michal Hocko sent a fix yesterday:
http://www.spinics.net/lists/linux-mm/msg121252.html
next prev parent reply other threads:[~2017-02-03 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 10:23 next-20170202 build: 4 failures 7 warnings (next-20170202) Build bot for Mark Brown
2017-02-02 23:08 ` Paul Gortmaker
2017-02-03 12:01 ` Mark Brown
2017-02-03 16:44 ` Mike Rapoport [this message]
2017-02-03 17:04 ` Arnd Bergmann
2017-02-03 17:21 ` Michal Hocko
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=20170203164442.GA3183@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=paul.gortmaker@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox