public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Felipe Balbi <balbi@ti•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Andrzej Pietrasiewicz <andrzej.p@samsung•com>
Subject: linux-next: build warnings after merge of the usb-gadget tree
Date: Wed, 20 May 2015 16:29:37 +1000	[thread overview]
Message-ID: <20150520162937.5cca5b00@canb.auug.org.au> (raw)

[-- 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 --]

             reply	other threads:[~2015-05-20  6:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  6:29 Stephen Rothwell [this message]
2015-05-20  7:18 ` linux-next: build warnings after merge of the usb-gadget tree Andrzej Pietrasiewicz
  -- 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=20150520162937.5cca5b00@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=andrzej.p@samsung$(echo .)com \
    --cc=balbi@ti$(echo .)com \
    --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