Re: next-20170202 build: 4 failures 7 warnings (next-20170202)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri 03-02-17 18:04:41, Arnd Bergmann wrote:
> On Fri, Feb 3, 2017 at 5:44 PM, Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx> wrote:
> 
> >> >     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
> 
> Sorry I missed that, and sent another copy now. It seems that Michal
> only fixed mm/nommu.c though, while I caught another hunk in ipc/shm.c
> that also needs to be fixed.

I have missed that one because the microblaze allnoconfig doesn't have
CONFIG_SYSVIPC enabled. Thanks for catching that.
 
> Let me know if I should resend that one line change by itself.

ip/shm.c fix up should be sent to Andrew so that he can fold it into the
original patch.
-- 
Michal Hocko
SUSE Labs
--
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



[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux