From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: linux-next: build warnings after merge of the usb tree
Date: Thu, 14 Apr 2011 14:18:31 +1000 [thread overview]
Message-ID: <20110414141831.16796e84.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2314 bytes --]
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/usb/renesas_usbhs/pipe.c: In function 'usbhsp_pipectrl_set':
drivers/usb/renesas_usbhs/pipe.c:81: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:81: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c: In function 'usbhsp_pipectrl_get':
drivers/usb/renesas_usbhs/pipe.c:92: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:92: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c: In function 'usbhsp_pipe_select':
drivers/usb/renesas_usbhs/pipe.c:180: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:180: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c: In function 'usbhsp_fifo_select':
drivers/usb/renesas_usbhs/pipe.c:350: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:350: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c: In function 'usbhsp_setup_pipebuff':
drivers/usb/renesas_usbhs/pipe.c:604: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:604: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c: In function 'usbhs_pipe_malloc':
drivers/usb/renesas_usbhs/pipe.c:775: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:775: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:775: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
drivers/usb/renesas_usbhs/pipe.c:795: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:795: warning: cast from pointer to integer of different size
drivers/usb/renesas_usbhs/pipe.c:795: warning: format '%d' expects type 'int', but argument 4 has type 'long unsigned int'
Introduced by commit f1407d5c6624 ("usb: renesas_usbhs: Add Renesas USBHS
common code").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-04-14 4:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 4:18 Stephen Rothwell [this message]
2011-04-14 4:51 ` linux-next: build warnings after merge of the usb tree Greg KH
2017-11-02 4:10 Stephen Rothwell
2017-11-02 8:45 ` Greg KH
2020-01-07 3:30 Stephen Rothwell
2020-01-07 8:06 ` Krzysztof Kozlowski
2020-01-21 6:28 ` Stephen Rothwell
2020-01-21 7:55 ` Krzysztof Kozlowski
2020-03-17 7:57 Stephen Rothwell
2020-03-17 13:45 ` Andrey Konovalov
2020-03-17 13:53 ` Greg KH
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=20110414141831.16796e84.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).