All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Pietrasiewicz <andrzej.p@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Felipe Balbi <balbi@ti.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the usb-gadget tree
Date: Wed, 20 May 2015 09:18:45 +0200	[thread overview]
Message-ID: <555C3555.5030400@samsung.com> (raw)
In-Reply-To: <20150520162937.5cca5b00@canb.auug.org.au>

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

  reply	other threads:[~2015-05-20  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-14  2:36 Stephen Rothwell

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=555C3555.5030400@samsung.com \
    --to=andrzej.p@samsung.com \
    --cc=balbi@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.