From: Build bot for Mark Brown <broonie@kernel.org>
To: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: v4.7.5 build: 0 failures 2 warnings (v4.7.5)
Date: Sat, 24 Sep 2016 14:44:46 +0100 [thread overview]
Message-ID: <E1bnnG2-0003u3-OW@optimist> (raw)
Tree/Branch: v4.7.5
Git describe: v4.7.5
Commit: 6c21842b5f Linux 4.7.5
Build Time: 71 min 4 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 : x86_64-defconfig
1 warnings 0 mismatches : arm-multi_v7_defconfig
1 warnings 0 mismatches : arm-allmodconfig
1 warnings 0 mismatches : arm64-defconfig
-------------------------------------------------------------------------------
Warnings Summary: 2
5 ../fs/nfs/nfs4session.c:201:54: warning: 'cur_seq' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized]
===============================================================================
Detailed per-defconfig build reports below:
-------------------------------------------------------------------------------
arm64-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
../fs/nfs/nfs4session.c:201:54: warning: 'cur_seq' 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]
-------------------------------------------------------------------------------
x86_64-defconfig : PASS, 0 errors, 1 warnings, 0 section mismatches
Warnings:
../fs/nfs/nfs4session.c:201:54: warning: 'cur_seq' may be used uninitialized in this function [-Wmaybe-uninitialized]
-------------------------------------------------------------------------------
arm-multi_v7_defconfig : PASS, 0 errors, 1 warnings, 0 section mismatches
Warnings:
../fs/nfs/nfs4session.c:201:54: warning: 'cur_seq' may be used uninitialized in this function [-Wmaybe-uninitialized]
-------------------------------------------------------------------------------
arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches
Warnings:
../fs/nfs/nfs4session.c:201:54: warning: 'cur_seq' may be used uninitialized in this function [-Wmaybe-uninitialized]
-------------------------------------------------------------------------------
arm64-defconfig : PASS, 0 errors, 1 warnings, 0 section mismatches
Warnings:
../fs/nfs/nfs4session.c:201:54: warning: 'cur_seq' may be used uninitialized in this function [-Wmaybe-uninitialized]
-------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
x86_64-allnoconfig
arm64-allnoconfig
arm-allnoconfig
arm-multi_v5_defconfig
next reply other threads:[~2016-09-24 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 13:44 Build bot for Mark Brown [this message]
2016-09-24 20:57 ` v4.7.5 build: 0 failures 2 warnings (v4.7.5) Arnd Bergmann
2016-09-25 13:27 ` Greg KH
2016-09-25 15:03 ` Greg KH
2016-09-25 23:46 ` Arnd Bergmann
2016-09-26 9:01 ` Greg KH
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=E1bnnG2-0003u3-OW@optimist \
--to=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=stable@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.