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: v3.6.11 build: 2 failures 11 warnings (v3.6.11)
Date: Sat, 22 Oct 2016 07:42:24 +0100 [thread overview]
Message-ID: <E1bxq0d-0007gv-Ex@optimist> (raw)
Tree/Branch: v3.6.11
Git describe: v3.6.11
Commit: b2824f4e09 Linux 3.6.11
Build Time: 0 min 16 sec
Passed: 2 / 4 ( 50.00 %)
Failed: 2 / 4 ( 50.00 %)
Errors: 1
Warnings: 11
Section Mismatches: 0
Failed defconfigs:
arm-allmodconfig
arm-allnoconfig
Errors:
arm-allnoconfig
/home/broonie/build/linux-stable/include/linux/compiler-gcc.h:100:30: fatal error: linux/compiler-gcc5.h: No such file or directory
-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
10 warnings 0 mismatches : x86_64-allnoconfig
2 warnings 0 mismatches : arm-allmodconfig
3 warnings 0 mismatches : x86_64-defconfig
-------------------------------------------------------------------------------
Errors summary: 1
1 /home/broonie/build/linux-stable/include/linux/compiler-gcc.h:100:30: fatal error: linux/compiler-gcc5.h: No such file or directory
Warnings Summary: 11
2 /home/broonie/build/linux-stable/scripts/sortextable.h:158:3: warning: 'relocs_size' may be used uninitialized in this function [-Wmaybe-uninitialized]
2 /home/broonie/build/linux-stable/fs/namespace.c:2433:8: warning: 'kernel_type' may be used uninitialized in this function [-Wmaybe-uninitialized]
2 /home/broonie/build/linux-stable/fs/namespace.c:2433:8: warning: 'kernel_dev' may be used uninitialized in this function [-Wmaybe-uninitialized]
2 .config:20:warning: symbol value '' invalid for PHYS_OFFSET
1 /home/broonie/build/linux-stable/fs/compat_ioctl.c:611:38: warning: typedef 'SS' locally defined but not used [-Wunused-local-typedefs]
1 /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:407:21: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:367:4: warning: 'd' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:361:4: warning: 'b' is used uninitialized in this function [-Wuninitialized]
1 /home/broonie/build/linux-stable/arch/x86/kernel/cpu/perf_event_intel_uncore.c:164:2: warning: 'count' is used uninitialized in this function [-Wuninitialized]
1 /home/broonie/build/linux-stable/arch/x86/kernel/cpu/perf_event_intel_uncore.c:135:9: warning: 'config' is used uninitialized in this function [-Wuninitialized]
1 /home/broonie/build/linux-stable/arch/x86/kernel/cpu/perf_event_intel_uncore.c:124:9: warning: 'config' is used uninitialized in this function [-Wuninitialized]
===============================================================================
Detailed per-defconfig build reports below:
-------------------------------------------------------------------------------
x86_64-allnoconfig : PASS, 0 errors, 10 warnings, 0 section mismatches
Warnings:
/home/broonie/build/linux-stable/scripts/sortextable.h:158:3: warning: 'relocs_size' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/broonie/build/linux-stable/scripts/sortextable.h:158:3: warning: 'relocs_size' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:361:4: warning: 'b' is used uninitialized in this function [-Wuninitialized]
/home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:367:4: warning: 'd' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:407:21: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/broonie/build/linux-stable/arch/x86/kernel/cpu/perf_event_intel_uncore.c:124:9: warning: 'config' is used uninitialized in this function [-Wuninitialized]
/home/broonie/build/linux-stable/arch/x86/kernel/cpu/perf_event_intel_uncore.c:135:9: warning: 'config' is used uninitialized in this function [-Wuninitialized]
/home/broonie/build/linux-stable/arch/x86/kernel/cpu/perf_event_intel_uncore.c:164:2: warning: 'count' is used uninitialized in this function [-Wuninitialized]
/home/broonie/build/linux-stable/fs/namespace.c:2433:8: warning: 'kernel_dev' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/broonie/build/linux-stable/fs/namespace.c:2433:8: warning: 'kernel_type' may be used uninitialized in this function [-Wmaybe-uninitialized]
-------------------------------------------------------------------------------
arm-allmodconfig : FAIL, 0 errors, 2 warnings, 0 section mismatches
Warnings:
.config:20:warning: symbol value '' invalid for PHYS_OFFSET
.config:20:warning: symbol value '' invalid for PHYS_OFFSET
-------------------------------------------------------------------------------
arm-allnoconfig : FAIL, 1 errors, 0 warnings, 0 section mismatches
Errors:
/home/broonie/build/linux-stable/include/linux/compiler-gcc.h:100:30: fatal error: linux/compiler-gcc5.h: No such file or directory
-------------------------------------------------------------------------------
x86_64-defconfig : PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
/home/broonie/build/linux-stable/fs/namespace.c:2433:8: warning: 'kernel_dev' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/broonie/build/linux-stable/fs/namespace.c:2433:8: warning: 'kernel_type' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/broonie/build/linux-stable/fs/compat_ioctl.c:611:38: warning: typedef 'SS' locally defined but not used [-Wunused-local-typedefs]
-------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
reply other threads:[~2016-10-22 6:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1bxq0d-0007gv-Ex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox