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@xxxxxxxxxxxxxxxxxx> > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
