v4.4.14 build: 0 failures 1 warnings (v4.4.14)

Tree/Branch: v4.4.14
Git describe: v4.4.14
Commit: 9ca1d50fa9 Linux 4.4.14

Build Time: 121 min 37 sec

Passed:    9 / 9   (100.00 %)
Failed:    0 / 9   (  0.00 %)

Errors: 0
Warnings: 1
Section Mismatches: 0

-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
1 warnings 0 mismatches : arm64-allmodconfig

-------------------------------------------------------------------------------

Warnings Summary: 1
1 ../drivers/xen/balloon.c:155:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function]

===============================================================================
Detailed per-defconfig build reports below:

-------------------------------------------------------------------------------
arm64-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches

Warnings:
../drivers/xen/balloon.c:155:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function]
-------------------------------------------------------------------------------

Passed with no errors, warnings or mismatches:

arm64-allnoconfig
arm-multi_v5_defconfig
arm-multi_v7_defconfig
x86_64-defconfig
arm-allmodconfig
arm-allnoconfig
x86_64-allnoconfig
arm64-defconfig
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr

Hi Greg,

It seems we're down to a single warning on ARM and ARM64 now, and the fix just got merged as commit

842775f15090 ("xen/balloon: Fix declared-but-not-defined warning")

so we can for the first time have a stable kernel that builds without warnings on these architectures, nice!

On 4.7-rc, there are currently two warnings:

The first one is an old issue that gcc recently started warning for, a workaround (reiserfs: fix "new_insert_key may be used uninitialized ...") is currently in Andrew's akpm-current, but I think it's not planned for 4.7 since it's not a regression and the code works correctly.

The second one is a real bug, and the fix is now in the staging-linus tree.

Arnd

This is now queued up, thanks for pushing for these, it's great to see.

thanks,

greg k-h