From: Lee Jones <lee.jones@linaro.org>
To: Pankaj Dubey <pankaj.dubey@samsung.com>
Cc: linux-kernel@vger.kernel.org, sameo@linux.intel.com, sbkim73@samsung.com
Subject: Re: [PATCH] drivers: mfd: silence compiler warning in sec-core.c
Date: Mon, 10 Mar 2014 15:07:00 +0000 [thread overview]
Message-ID: <20140310150700.GC13661@lee--X1> (raw)
In-Reply-To: <1394017159-4851-1-git-send-email-pankaj.dubey@samsung.com>
> When used 64bit compiler GCC warns as
> drivers/mfd/sec-core.c:199:10: warning:
> cast from pointer to integer of different size [-Wpointer-to-int-cast]
>
> This patch fixes this by type-casting "match->data" into "long" before
> converting into "int"
>
> Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> ---
> drivers/mfd/sec-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/sec-core.c b/drivers/mfd/sec-core.c
> index a139798..2e7580bd 100644
> --- a/drivers/mfd/sec-core.c
> +++ b/drivers/mfd/sec-core.c
> @@ -187,7 +187,7 @@ static inline int sec_i2c_get_driver_data(struct i2c_client *i2c,
> if (i2c->dev.of_node) {
> const struct of_device_id *match;
> match = of_match_node(sec_dt_match, i2c->dev.of_node);
> - return (int)match->data;
> + return (int)(long)match->data;
I think using an unsigned long would be better.
> }
> #endif
> return (int)id->driver_data;
Doesn't this give you the same error?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-03-10 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 10:59 [PATCH] drivers: mfd: silence compiler warning in sec-core.c Pankaj Dubey
2014-03-10 15:07 ` Lee Jones [this message]
2014-03-11 2:28 ` Pankaj Dubey
2014-03-11 6:46 ` Lee Jones
2014-03-12 6:37 ` [PATCH v2] " Pankaj Dubey
2014-03-12 9:43 ` Lee Jones
2014-03-13 2:14 ` [PATCH v3] " Pankaj Dubey
2014-03-13 8:03 ` Lee Jones
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=20140310150700.GC13661@lee--X1 \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=sameo@linux.intel.com \
--cc=sbkim73@samsung.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 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.