All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Gautam <gautam.vivek@samsung.com>
To: linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	Fengguang Wu <fengguang.wu@intel.com>,
	Christopher Li <sparse@chrisli.org>, Felipe Balbi <balbi@ti.com>
Subject: [PATCH] usb: phy: samsung-usb2: Fix sparse warning
Date: Tue, 19 Mar 2013 14:45:17 +0530	[thread overview]
Message-ID: <1363684517-10354-1-git-send-email-gautam.vivek@samsung.com> (raw)

Fixing the following sparse warning:

sparse warnings: (new ones prefixed by >>)

>> drivers/usb/phy/phy-samsung-usb2.c:50:26: sparse: incorrect type in argument 1 (different address spaces)
   drivers/usb/phy/phy-samsung-usb2.c:50:26:    expected void const volatile [noderef] <asn:2>*addr
   drivers/usb/phy/phy-samsung-usb2.c:50:26:    got void *
>> drivers/usb/phy/phy-samsung-usb2.c:73:35: sparse: incorrect type in argument 1 (different address spaces)
   drivers/usb/phy/phy-samsung-usb2.c:73:35:    expected void *regs
   drivers/usb/phy/phy-samsung-usb2.c:73:35:    got void [noderef] <asn:2>*regs

Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
CC: Fengguang Wu <fengguang.wu@intel.com>
CC: Christopher Li <sparse@chrisli.org>
CC: Felipe Balbi <balbi@ti.com>
---

Based on 'next' branch of Felipe's usb tree.
Tested using make C=2 drivers/usb/phy/phy-samsung-usb2.o

Hi Felipe,

Sorry to bug you for this small change, i think this got unnoticed in the
last cycle too. Fixing it now.

Thanks
Vivek

 drivers/usb/phy/phy-samsung-usb2.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/usb/phy/phy-samsung-usb2.c b/drivers/usb/phy/phy-samsung-usb2.c
index dce9681..45ffe03 100644
--- a/drivers/usb/phy/phy-samsung-usb2.c
+++ b/drivers/usb/phy/phy-samsung-usb2.c
@@ -43,7 +43,7 @@ static int samsung_usbphy_set_host(struct usb_otg *otg, struct usb_bus *host)
 	return 0;
 }
 
-static bool exynos5_phyhost_is_on(void *regs)
+static bool exynos5_phyhost_is_on(void __iomem *regs)
 {
 	u32 reg;
 
-- 
1.7.6.5


                 reply	other threads:[~2013-03-19  9:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1363684517-10354-1-git-send-email-gautam.vivek@samsung.com \
    --to=gautam.vivek@samsung.com \
    --cc=balbi@ti.com \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sparse@chrisli.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 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.