* linux-next: build warnings after merge of the usb-gadget tree
@ 2015-05-20 6:29 Stephen Rothwell
2015-05-20 7:18 ` Andrzej Pietrasiewicz
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2015-05-20 6:29 UTC (permalink / raw)
To: Felipe Balbi; +Cc: linux-next, linux-kernel, Andrzej Pietrasiewicz
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Hi Felipe,
After merging the usb-gadget tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/usb/gadget/function/rndis.c: In function 'rndis_proc_write':
drivers/usb/gadget/function/rndis.c:1147:4: warning: passing argument 1 of 'rndis_signal_connect' makes pointer from integer without a cast
rndis_signal_connect(p->confignr);
^
drivers/usb/gadget/function/rndis.c:748:5: note: expected 'struct rndis_params *' but argument is of type 'u8'
int rndis_signal_connect(struct rndis_params *params)
^
drivers/usb/gadget/function/rndis.c:1151:4: warning: passing argument 1 of 'rndis_signal_disconnect' makes pointer from integer without a cast
rndis_signal_disconnect(p->confignr);
^
drivers/usb/gadget/function/rndis.c:755:5: note: expected 'struct rndis_params *' but argument is of type 'u8'
int rndis_signal_disconnect(struct rndis_params *params)
^
Probably caused by commit 83210e59ee15 ("usb: gadget: rndis: use
rndis_params instead of configNr").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: build warnings after merge of the usb-gadget tree
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
0 siblings, 0 replies; 3+ messages in thread
From: Andrzej Pietrasiewicz @ 2015-05-20 7:18 UTC (permalink / raw)
To: Stephen Rothwell, Felipe Balbi; +Cc: linux-next, linux-kernel
W dniu 20.05.2015 o 08:29, Stephen Rothwell pisze:
> Hi Felipe,
>
> After merging the usb-gadget tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> drivers/usb/gadget/function/rndis.c: In function 'rndis_proc_write':
> drivers/usb/gadget/function/rndis.c:1147:4: warning: passing argument 1 of 'rndis_signal_connect' makes pointer from integer without a cast
> rndis_signal_connect(p->confignr);
> ^
> drivers/usb/gadget/function/rndis.c:748:5: note: expected 'struct rndis_params *' but argument is of type 'u8'
> int rndis_signal_connect(struct rndis_params *params)
> ^
> drivers/usb/gadget/function/rndis.c:1151:4: warning: passing argument 1 of 'rndis_signal_disconnect' makes pointer from integer without a cast
> rndis_signal_disconnect(p->confignr);
> ^
> drivers/usb/gadget/function/rndis.c:755:5: note: expected 'struct rndis_params *' but argument is of type 'u8'
> int rndis_signal_disconnect(struct rndis_params *params)
> ^
>
> Probably caused by commit 83210e59ee15 ("usb: gadget: rndis: use
> rndis_params instead of configNr").
>
There is already a patch series for that:
http://www.spinics.net/lists/linux-usb/msg125003.html
AP
^ permalink raw reply [flat|nested] 3+ messages in thread
* linux-next: build warnings after merge of the usb-gadget tree
@ 2016-11-14 2:36 Stephen Rothwell
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2016-11-14 2:36 UTC (permalink / raw)
To: Felipe Balbi; +Cc: linux-next, linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-11-14 2:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2016-11-14 2:36 Stephen Rothwell
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).