From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Felipe Balbi <balbi@kernel•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build warnings after merge of the usb-gadget tree
Date: Mon, 14 Nov 2016 13:36:49 +1100 [thread overview]
Message-ID: <20161114133649.348eb08e@canb.auug.org.au> (raw)
Hi Felipe,
After merging the usb-gadget tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/staging/iio/frequency/ad9832.c: In function 'ad9832_probe':
drivers/staging/iio/frequency/ad9832.c:214:11: warning: 'st' may be used uninitialized in this function [-Wmaybe-uninitialized]
st->avdd = devm_regulator_get(&spi->dev, "avdd");
^
This was probably because -Wmaybe-uninitialized has been reenabled in Linus' tree
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c:35:0:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: warning: "mutex_lock_interruptible" redefined
#define mutex_lock_interruptible mutex_lock_interruptible_killable
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h:37:0,
from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c:34:
include/linux/mutex.h:161:0: note: this is the location of the previous definition
#define mutex_lock_interruptible(lock) mutex_lock_interruptible_nested(lock, 0)
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_kern_lib.c:42:0:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: warning: "mutex_lock_interruptible" redefined
#define mutex_lock_interruptible mutex_lock_interruptible_killable
^
In file included from include/linux/notifier.h:13:0,
from include/linux/memory_hotplug.h:6,
from include/linux/mmzone.h:751,
from include/linux/gfp.h:5,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_kern_lib.c:37:
include/linux/mutex.h:161:0: note: this is the location of the previous definition
#define mutex_lock_interruptible(lock) mutex_lock_interruptible_nested(lock, 0)
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c:56:0:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: warning: "mutex_lock_interruptible" redefined
#define mutex_lock_interruptible mutex_lock_interruptible_killable
^
In file included from include/linux/notifier.h:13:0,
from include/linux/memory_hotplug.h:6,
from include/linux/mmzone.h:751,
from include/linux/gfp.h:5,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c:36:
include/linux/mutex.h:161:0: note: this is the location of the previous definition
#define mutex_lock_interruptible(lock) mutex_lock_interruptible_nested(lock, 0)
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c:53:0:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: warning: "mutex_lock_interruptible" redefined
#define mutex_lock_interruptible mutex_lock_interruptible_killable
^
In file included from arch/x86/include/asm/mmu.h:5:0,
from arch/x86/include/asm/acpi.h:31,
from arch/x86/include/asm/fixmap.h:19,
from arch/x86/include/asm/apic.h:11,
from arch/x86/include/asm/smp.h:12,
from include/linux/smp.h:59,
from include/linux/percpu.h:6,
from include/linux/context_tracking_state.h:4,
from include/linux/vtime.h:4,
from include/linux/hardirq.h:7,
from include/linux/interrupt.h:12,
from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c:37:
include/linux/mutex.h:161:0: note: this is the location of the previous definition
#define mutex_lock_interruptible(lock) mutex_lock_interruptible_nested(lock, 0)
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_kern_lib.c:42:0:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: warning: "mutex_lock_interruptible" redefined
#define mutex_lock_interruptible mutex_lock_interruptible_killable
^
In file included from include/linux/notifier.h:13:0,
from include/linux/memory_hotplug.h:6,
from include/linux/mmzone.h:751,
from include/linux/gfp.h:5,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_kern_lib.c:37:
include/linux/mutex.h:161:0: note: this is the location of the previous definition
#define mutex_lock_interruptible(lock) mutex_lock_interruptible_nested(lock, 0)
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_util.c:35:0:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: warning: "mutex_lock_interruptible" redefined
#define mutex_lock_interruptible mutex_lock_interruptible_killable
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_util.h:39:0,
from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_util.c:34:
include/linux/mutex.h:161:0: note: this is the location of the previous definition
#define mutex_lock_interruptible(lock) mutex_lock_interruptible_nested(lock, 0)
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_connected.c:36:0:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: warning: "mutex_lock_interruptible" redefined
#define mutex_lock_interruptible mutex_lock_interruptible_killable
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h:37:0,
from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_connected.c:35:
include/linux/mutex.h:161:0: note: this is the location of the previous definition
#define mutex_lock_interruptible(lock) mutex_lock_interruptible_nested(lock, 0)
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_connected.c:36:0:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: warning: "mutex_lock_interruptible" redefined
#define mutex_lock_interruptible mutex_lock_interruptible_killable
^
In file included from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h:37:0,
from drivers/staging/vc04_services/interface/vchiq_arm/vchiq_connected.c:35:
include/linux/mutex.h:161:0: note: this is the location of the previous definition
#define mutex_lock_interruptible(lock) mutex_lock_interruptible_nested(lock, 0)
^
I am not sure where the reset of these came from.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-11-14 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 2:36 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-20 6:29 linux-next: build warnings after merge of the usb-gadget tree Stephen Rothwell
2015-05-20 7:18 ` Andrzej Pietrasiewicz
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=20161114133649.348eb08e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=balbi@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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