From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: Build bot for Mark Brown <broonie@kernel.org>,
kernel-build-reports@lists.linaro.org,
linux-next@vger.kernel.org, Liviu Dudau <Liviu.Dudau@arm.com>
Subject: Re: next-20160602 build: 0 failures 2 warnings (next-20160602)
Date: Thu, 02 Jun 2016 11:58:24 +0200 [thread overview]
Message-ID: <7858362.3LIbrZdxpY@wuerfel> (raw)
In-Reply-To: <E1b8PEc-0000qk-Ol@optimist>
On Thursday, June 2, 2016 10:48:15 AM CEST Build bot for Mark Brown wrote:
> Tree/Branch: next-20160602
> Git describe: next-20160602
> Commit: ce425f36d1 Add linux-next specific files for 20160602
>
> Build Time: 141 min 21 sec
>
> Passed: 9 / 9 (100.00 %)
> Failed: 0 / 9 ( 0.00 %)
>
> Errors: 0
> Warnings: 2
> Section Mismatches: 0
>
> -------------------------------------------------------------------------------
> defconfigs with issues (other than build errors):
> 2 warnings 0 mismatches : arm64-allmodconfig
> 1 warnings 0 mismatches : arm-allmodconfig
>
> -------------------------------------------------------------------------------
>
> Warnings Summary: 2
> 2 ../drivers/gpu/drm/arm/hdlcd_crtc.c:185:28: warning: unused variable 'hdlcd' [-Wunused-variable]
This was introduced today by 1e5e10b59403 ("drm: hdlcd: Cleanup the atomic plane operations").
Liviu, can you fix it up?
> 1 ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized]
I sent a patch on Monday, but Greg has been busy working on his stable kernels,
I'm sure he'll get to it.
Arnd
next prev parent reply other threads:[~2016-06-02 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 9:48 next-20160602 build: 0 failures 2 warnings (next-20160602) Build bot for Mark Brown
2016-06-02 9:58 ` Arnd Bergmann [this message]
2016-06-02 10:08 ` Liviu Dudau
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=7858362.3LIbrZdxpY@wuerfel \
--to=arnd@arndb.de \
--cc=Liviu.Dudau@arm.com \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.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.