From: Arnd Bergmann <arnd@arndb.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
Olof's autobuilder <build@lixom.net>,
olof@lixom.net, linuxppc-dev@lists.ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Walleij <linus.ml.walleij@gmail.com>,
linux-kernel@vger.kernel.org,
Stefano Stabellini <sstabellini@kernel.org>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
Dave Chinner <david@fromorbit.com>,
Krzysztof Kozlowski <k.kozlowski.k@gmail.com>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: next build: 37 warnings 2 failures (next/next-20160519)
Date: Thu, 19 May 2016 15:14:20 +0200 [thread overview]
Message-ID: <2590345.NrfsVLDrUS@wuerfel> (raw)
In-Reply-To: <20160519092044.GI26110@dhcp22.suse.cz>
On Thursday 19 May 2016 11:20:44 Michal Hocko wrote:
> On Thu 19-05-16 11:07:09, Arnd Bergmann wrote:
> [...]
> > > 6 mm/page_alloc.c:3651:6: warning: 'compact_result' may be used uninitialized in this function [-Wmaybe-uninitialized]
> >
> > I'm surprised this one is still there, I sent a patch but Michal Hocko came up with
> > a better fix on May 12, which was not applied yet.
> >
> > Michael, can you resend this one to Andrew? I suspect he missed it as it was
> > sent as a reply to mine.
>
> Andrew has taken the patch IIRC but he hasn't released any mmotm since
> then so it didn't get to the linux-next.
>
Ok, cool, that explains it.
Arnd
next prev parent reply other threads:[~2016-05-19 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <573d6f0c.8664620a.24f8e.ffff931b@mx.google.com>
2016-05-19 9:07 ` next build: 37 warnings 2 failures (next/next-20160519) Arnd Bergmann
2016-05-19 9:20 ` Michal Hocko
2016-05-19 13:14 ` Arnd Bergmann [this message]
2016-05-19 9:33 ` Kishon Vijay Abraham I
2016-05-19 13:15 ` Arnd Bergmann
2016-05-19 10:24 ` Stefano Stabellini
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=2590345.NrfsVLDrUS@wuerfel \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=build@lixom.net \
--cc=david@fromorbit.com \
--cc=k.kozlowski.k@gmail.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kishon@ti.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@kernel.org \
--cc=olof@lixom.net \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
/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.