From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org,
linux-next@vger.kernel.org
Subject: Re: next-20160512 build: 0 failures 18 warnings (next-20160512)
Date: Thu, 12 May 2016 11:55:29 +0100 [thread overview]
Message-ID: <20160512105529.GA6261@sirena.org.uk> (raw)
In-Reply-To: <6651930.C0tGb7p3a4@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
On Thu, May 12, 2016 at 11:14:35AM +0200, Arnd Bergmann wrote:
> On Thursday 12 May 2016 09:38:52 Build bot for Mark Brown wrote:
> > ../fs/gfs2/dir.c:1021:8: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]
> > ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized]
> > ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized]
> I should check these all, these may have been uncovered by my change to not
> set CONFIG_CC_OPTIMIZE_FOR_SIZE for allmodconfig, which dropped the
> -Wno-maybe-uninitialized.
> Which compiler version are you using?
For v8 it's currently aarch64-linux-gnu-gcc (Linaro GCC 5.1-2015.08)
5.1.1 20150608.
> > ../drivers/regulator/core.c:2536:1: warning: 'regulator_can_change_voltage' is deprecated [-Wdeprecated-declarations]
> Mark, are you planning to remove the definition for 4.7 when we get there?
> If not, maybe do a change so we don't get a warning for the EXPORT_SYMBOL?
Once the users are gone the function will go.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-05-12 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 8:38 next-20160512 build: 0 failures 18 warnings (next-20160512) Build bot for Mark Brown
2016-05-12 9:14 ` Arnd Bergmann
2016-05-12 10:55 ` Mark Brown [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=20160512105529.GA6261@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).