From: Michal Hocko <mhocko@kernel•org>
To: Arnd Bergmann <arnd@arndb•de>
Cc: Mike Rapoport <rppt@linux•vnet.ibm.com>,
Mark Brown <broonie@kernel•org>,
linaro-kernel@lists•linaro.org,
kernel-build-reports@lists•linaro.org,
Hillf Danton <hillf.zj@alibaba-inc•com>,
Paul Gortmaker <paul.gortmaker@windriver•com>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: next-20170202 build: 4 failures 7 warnings (next-20170202)
Date: Fri, 3 Feb 2017 18:21:12 +0100 [thread overview]
Message-ID: <20170203172110.GK19325@dhcp22.suse.cz> (raw)
In-Reply-To: <CAK8P3a3MkTfHyHi=ggrvygV-tCSP+2=jNuT_kX-GKt5d=FYtkQ@mail.gmail.com>
On Fri 03-02-17 18:04:41, Arnd Bergmann wrote:
> On Fri, Feb 3, 2017 at 5:44 PM, Mike Rapoport <rppt@linux•vnet.ibm.com> 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
prev parent reply other threads:[~2017-02-03 17:21 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
2017-02-03 17:04 ` Arnd Bergmann
2017-02-03 17:21 ` Michal Hocko [this message]
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=20170203172110.GK19325@dhcp22.suse.cz \
--to=mhocko@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=broonie@kernel$(echo .)org \
--cc=hillf.zj@alibaba-inc$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=rppt@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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