From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] usb: omap_control_usb: fix compile warning
Date: Wed, 6 Feb 2013 18:58:51 +0530 [thread overview]
Message-ID: <1360157331-9048-6-git-send-email-kishon@ti.com> (raw)
In-Reply-To: <1360157331-9048-1-git-send-email-kishon@ti.com>
From: Felipe Balbi <balbi@ti.com>
When CONFIG_OMAP_CONTROL_USB isn't enabled,
there's a compile warning stating that a
particular function isn't a prototype.
Fix it.
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
include/linux/usb/omap_control_usb.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/usb/omap_control_usb.h b/include/linux/usb/omap_control_usb.h
index f306db7..27b5b8c 100644
--- a/include/linux/usb/omap_control_usb.h
+++ b/include/linux/usb/omap_control_usb.h
@@ -70,7 +70,7 @@ extern void omap_control_usb3_phy_power(struct device *dev, bool on);
extern void omap_control_usb_set_mode(struct device *dev,
enum omap_control_usb_mode mode);
#else
-static inline struct device *omap_get_control_dev()
+static inline struct device *omap_get_control_dev(void)
{
return ERR_PTR(-ENODEV);
}
--
1.7.10.4
prev parent reply other threads:[~2013-02-06 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 13:28 [PATCH v2 0/5] ARM: OMAP: arm part of usb patches Kishon Vijay Abraham I
2013-02-06 13:28 ` [PATCH v2 1/5] ARM: OMAP4: remove control module address space from PHY and OTG Kishon Vijay Abraham I
2013-02-06 13:28 ` [PATCH v2 2/5] ARM: OMAP: devices: create device for usb part of control module Kishon Vijay Abraham I
2013-02-06 13:28 ` [PATCH v2 3/5] ARM: OMAP2: MUSB: Specify omap4 has mailbox Kishon Vijay Abraham I
2013-02-06 13:28 ` [PATCH v2 4/5] ARM: OMAP: USB: Add phy binding information Kishon Vijay Abraham I
2013-02-06 13:28 ` Kishon Vijay Abraham I [this message]
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=1360157331-9048-6-git-send-email-kishon@ti.com \
--to=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).