From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
kernel-build-reports@lists.linaro.org,
Stefano Stabellini <sstabellini@kernel.org>,
Linus Walleij <linus.ml.walleij@gmail.com>,
Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, Michal Hocko <mhocko@kernel.org>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
Krzysztof Kozlowski <k.kozlowski.k@gmail.com>,
olof@lixom.net, Andrew Morton <akpm@linux-foundation.org>,
Olof's autobuilder <build@lixom.net>
Subject: Re: next build: 37 warnings 2 failures (next/next-20160519)
Date: Thu, 19 May 2016 15:15:09 +0200 [thread overview]
Message-ID: <3230968.fKGkPFmYnk@wuerfel> (raw)
In-Reply-To: <573D886E.1050205@ti.com>
On Thursday 19 May 2016 15:03:34 Kishon Vijay Abraham I wrote:
> >
> >> 1 drivers/phy/phy-exynos-mipi-video.c:238:13: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized]
> >
> > I sent a patch on May 11, it was reviewed by Krzysztof Kozlowski, but not yet
> > applied.
>
> Is it okay if I send this during the -rc cycle?
>
Yes, it's a bug fix, so it should just go in as soon as possible, that's what
the -rc cycle is for after all.
Arnd
next prev parent reply other threads:[~2016-05-19 13:15 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
2016-05-19 9:33 ` Kishon Vijay Abraham I
2016-05-19 13:15 ` Arnd Bergmann [this message]
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=3230968.fKGkPFmYnk@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.