mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the Linus' tree
Date: Mon, 21 Nov 2011 09:25:06 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.1111210922090.10414@axis700.grange> (raw)
In-Reply-To: <20111121131701.44b49fc7da28170c9ee6b524@canb.auug.org.au>

Hi Stephen

On Mon, 21 Nov 2011, Stephen Rothwell wrote:

> Hi all,
> 
> Building Linus' tree today linux-next (x86_64_allmodconfig)
> produced quite a few of these warnings:
> 
> include/media/soc_camera.h: In function 'soc_camera_i2c_to_vdev':
> include/media/soc_camera.h:257:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> 
> This was introduced by commit 2f0babb7e432 ("[media] V4L: soc-camera:
> make (almost) all client drivers re-usable outside of the framework").
> 
> This warning is caused by the "grp_id" member of "struct v4l2_subdev" -
> which is a u32 - being cast to a pointer.  That pointer is dereferenced,
> so I have no idea how that is supposed to work on any 64 bit platform.

soc-camera atm supports 7 platforms (if I haven't forgotten anyone), none 
of them is 64-bit. But you're right, it shall compile cleanly on 64 bits 
too, I'm working on a patch. Unfortunately, while working on it I came 
across other regressions, that blocked my tests... But a solution will be 
found.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

  reply	other threads:[~2011-11-21  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  2:17 Stephen Rothwell
2011-11-21  8:25 ` Guennadi Liakhovetski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-26 22:58 Stephen Rothwell
2010-12-27  0:49 ` Jeff Garzik

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=Pine.LNX.4.64.1111210922090.10414@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®