From: Octavian Purdila <octavian.purdila@intel.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com,
Octavian Purdila <octavian.purdila@intel.com>,
Jun Tian <jun.j.tian@intel.com>, Alan Cox <alan@linux.intel.com>
Subject: [PATCH staging-next] goldfish: bus: fix warnings for 32bit builds
Date: Fri, 16 May 2014 08:24:58 +0300 [thread overview]
Message-ID: <1400217899-32261-1-git-send-email-octavian.purdila@intel.com> (raw)
drivers/platform/goldfish/pdev_bus.c: In function 'goldfish_new_pdev':
drivers/platform/goldfish/pdev_bus.c:136:14: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
writel((u32)(u64)name, pdev_bus_base + PDEV_BUS_GET_NAME);
Reported-by: Fengguang Wu <fengguang.wu@intel.com>
Cc: Jun Tian <jun.j.tian@intel.com>
Cc: Alan Cox <alan@linux.intel.com>
Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
---
drivers/platform/goldfish/pdev_bus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/goldfish/pdev_bus.c b/drivers/platform/goldfish/pdev_bus.c
index eb25440..8c43589 100644
--- a/drivers/platform/goldfish/pdev_bus.c
+++ b/drivers/platform/goldfish/pdev_bus.c
@@ -133,7 +133,7 @@ static int goldfish_new_pdev(void)
#ifdef CONFIG_64BIT
writel((u32)((u64)name>>32), pdev_bus_base + PDEV_BUS_GET_NAME_HIGH);
#endif
- writel((u32)(u64)name, pdev_bus_base + PDEV_BUS_GET_NAME);
+ writel((u32)(unsigned long)name, pdev_bus_base + PDEV_BUS_GET_NAME);
name[name_len] = '\0';
dev->pdev.id = readl(pdev_bus_base + PDEV_BUS_ID);
dev->pdev.resource[0].start = base;
--
1.8.3.2
next reply other threads:[~2014-05-16 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 5:24 Octavian Purdila [this message]
2014-05-16 5:24 ` [PATCH staging-next] goldfish: pipe: " Octavian Purdila
2014-05-16 9:17 ` Alan Cox
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=1400217899-32261-1-git-send-email-octavian.purdila@intel.com \
--to=octavian.purdila@intel.com \
--cc=alan@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=greg@kroah.com \
--cc=jun.j.tian@intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®