From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20151221 build: 2 failures 13 warnings (next-20151221)
Date: Mon, 21 Dec 2015 15:05:33 +0100 [thread overview]
Message-ID: <201512211505.34074.arnd@arndb.de> (raw)
In-Reply-To: <E1aAyjj-0007DR-4T@optimist>
Just looking at the remaining warnings/errors in linux-next:
On Monday 21 December 2015, Build bot for Mark Brown wrote:
> ../fs/orangefs/orangefs-kernel.h:773:2: error: implicit declaration of function 'ornagefs_inode_lock' [-Werror=implicit-function-declaration]
> ../fs/orangefs/orangefs-kernel.h:773:2: error: implicit declaration of function 'ornagefs_inode_lock' [-Werror=implicit-function-declaration]
> ../fs/orangefs/orangefs-kernel.h:773:2: error: implicit declaration of function 'ornagefs_inode_lock' [-Werror=implicit-function-declaration]
> ../fs/orangefs/orangefs-kernel.h:773:2: error: implicit declaration of function 'ornagefs_inode_lock' [-Werror=implicit-function-declaration]
I just sent a patch for this.
> arm64-allmodconfig : PASS, 0 errors, 5 warnings, 0 section mismatches
>
> Warnings:
> ../drivers/gpu/drm/vc4/vc4_validate.c:864:4: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t' [-Wformat=]
I have a trivial patch, need to send it out.
> ../drivers/staging/emxx_udc/emxx_udc.c:843:45: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> ../drivers/staging/emxx_udc/emxx_udc.c:1085:45: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> ../drivers/staging/emxx_udc/emxx_udc.c:2731:6: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
Submitted this one again last week, I had sent it a month ago, but the maintainer was busy.
> ../drivers/tty/serial/amba-pl011.c:190:27: warning: 'vendor_zte' defined but not used [-Wunused-variable]
rmk pointed out the problem when the patch was sent originally, no idea what we should do
about it other than reverting the patch that introduced the unused code.
> Warnings:
> <stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]
Not sure how we can improve this, the same thing seems to happen every time a new syscall gets
introduced. The actual change is trivial, but we need a better method to sync all architectures.
> ../kernel/printk/nmi.c:143:3: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'size_t' [-Wformat]
Sent a patch the other day.
> ../drivers/gpio/gpiolib.c:225:31: warning: 'iterator' may be used uninitialized in this function [-Wmaybe-uninitialized]
Introduced by Bamvor, currently discussing a solution with him and Linus. We can either shut up
the compiler or rewrite the function in a nicer way.
> arm-multi_v7_defconfig : PASS, 0 errors, 8 warnings, 0 section mismatches
>
> Warnings:
> arch/arm/configs/multi_v7_defconfig:433:warning: symbol value 'm' invalid for MFD_DA9063
I need to look into this, probably the result of a defconfig change we merged, but it's not
clear whether the driver should be a module, or the defconfig should have it built-in.
> ../net/bluetooth/mgmt.c:5471:8: warning: 'r192' may be used uninitialized in this function [-Wmaybe-uninitialized]
> ../net/bluetooth/mgmt.c:5471:8: warning: 'h192' may be used uninitialized in this function [-Wmaybe-uninitialized]
I don't see these with gcc-5.1
> ../crypto/wp512.c:987:1: warning: the frame size of 1112 bytes is larger than 1024 bytes [-Wframe-larger-than=]
no this one. If we want to fix it, it's probably best to change the
optimization level of the file, something gets misoptimzed here and it's
clear it should not use that much stack.
Arnd
next parent reply other threads:[~2015-12-21 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1aAyjj-0007DR-4T@optimist>
2015-12-21 14:05 ` Arnd Bergmann [this message]
2015-12-21 15:41 ` next-20151221 build: 2 failures 13 warnings (next-20151221) Mark Brown
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=201512211505.34074.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).