From: "H. Peter Anvin" <hpa@linux.intel.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Russell King" <rmk+kernel@arm.linux.org.uk>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: sound/pci/asihpi/hpioctl.c:125:6: warning: cast to pointer from integer of different size
Date: Thu, 07 Feb 2013 18:19:35 -0800 [thread overview]
Message-ID: <511460B7.4030007@linux.intel.com> (raw)
In-Reply-To: <51143ca4.bNX7TobZ2rDrz0zj%fengguang.wu@intel.com>
On 02/07/2013 03:45 PM, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/mm
> head: 6fcddf474ae1c8e2fb5f14c850c8aa018e7a5034
> commit: 6fcddf474ae1c8e2fb5f14c850c8aa018e7a5034 x86-32: Add support for 64bit get_user()
> date: 2 hours ago
> config: make ARCH=i386 allmodconfig
>
> All warnings:
>
> sound/pci/asihpi/hpioctl.c: In function 'asihpi_hpi_ioctl':
>>> sound/pci/asihpi/hpioctl.c:125:6: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>>> sound/pci/asihpi/hpioctl.c:126:6: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> --
> net/atm/resources.c: In function 'atm_dev_ioctl':
>>> net/atm/resources.c:223:8: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>>> net/atm/resources.c:274:7: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> --
[... and so on ...]
Now I remember this problem. I believe I discussed it with rmk in the
context of ARM, too. Russell, did we ever find any way to implement
8-byte get_user() on 32 bits without massive warning spewage?
-hpa
next parent reply other threads:[~2013-02-08 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51143ca4.bNX7TobZ2rDrz0zj%fengguang.wu@intel.com>
2013-02-08 2:19 ` H. Peter Anvin [this message]
2013-02-08 15:28 ` sound/pci/asihpi/hpioctl.c:125:6: warning: cast to pointer from integer of different size Russell King - ARM Linux
2013-02-08 17:06 ` H. Peter Anvin
2013-02-08 18:50 ` Ville Syrjälä
2013-02-08 22:57 ` Russell King - ARM Linux
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=511460B7.4030007@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=ville.syrjala@linux.intel.com \
/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).