From: Dirk Behme <dirk.behme@googlemail.com>
To: Felipe Balbi <felipebalbi@users.sourceforge.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: Fix warning in plat_uds.c
Date: Fri, 17 Aug 2007 18:39:05 +0200 [thread overview]
Message-ID: <46C5CF29.2020601@googlemail.com> (raw)
In-Reply-To: <31e679430708170912p1bd8050dg38db45d14d237961@mail.gmail.com>
Felipe Balbi wrote:
> Hi,
Thanks for review!
> On 8/17/07, Dirk Behme <dirk.behme@googlemail.com> wrote:
>
>>Fix warning
>>
>>drivers/usb/musb/plat_uds.c:1731: warning: 'dev_attr_srp' defined but
>>not used
>>
>>if CONFIG_USB_MUSB_OTG isn't set (DaVinci use case)
>>
>>Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>>
>>Index: linux-davinci/drivers/usb/musb/plat_uds.c
>>===================================================================
>>--- linux-davinci.orig/drivers/usb/musb/plat_uds.c
>>+++ linux-davinci/drivers/usb/musb/plat_uds.c
>>@@ -1707,6 +1707,7 @@ musb_vbus_show(struct device *dev, struc
>> }
>> static DEVICE_ATTR(vbus, 0644, musb_vbus_show, musb_vbus_store);
>>
>>+#ifdef CONFIG_USB_MUSB_OTG
>> static ssize_t
>> musb_srp_store(struct device *dev, struct device_attribute *attr,
>> const char *buf, size_t n)
>>@@ -1728,8 +1729,11 @@ musb_srp_store(struct device *dev, struc
>>
>> return n;
>> }
>>+
>>+
>> static DEVICE_ATTR(srp, 0644, NULL, musb_srp_store);
>> #endif
>>+#endif
>
>
> this doesn't look right since any device can issue SRP. It's better
> for you to use it somewhere on DaVinci.
Sorry, if I missed anything. Looking to recent plat_uds.c of OMAP,
dev_attr_srp is used at two places encapsulated by CONFIG_USB_MUSB_OTG:
#ifdef CONFIG_USB_MUSB_OTG
status = device_create_file(dev, &dev_attr_srp);
#endif /* CONFIG_USB_MUSB_OTG */
#ifdef CONFIG_USB_MUSB_OTG
device_remove_file(musb->controller, &dev_attr_srp);
#endif
I think that's the reason for warning
drivers/usb/musb/plat_uds.c:1731: warning: 'dev_attr_srp' defined but
not used
if CONFIG_USB_MUSB_OTG isn't set? What do do you propose instead to
get rid of this warning on OMAP?
Dirk
next prev parent reply other threads:[~2007-08-17 16:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 15:43 [PATCH] ARM: OMAP: Fix warning in plat_uds.c Dirk Behme
2007-08-17 16:12 ` Felipe Balbi
2007-08-17 16:39 ` Dirk Behme [this message]
2007-08-17 16:57 ` David Brownell
2007-08-17 18:14 ` Felipe Balbi
2007-08-17 18:30 ` David Brownell
2007-08-17 20:36 ` Felipe Balbi
2007-08-17 21:02 ` David Brownell
2007-08-20 6:51 ` Dirk Behme
2007-08-20 8:41 ` David Brownell
2007-08-20 9:59 ` Dirk Behme
2007-08-20 18:10 ` David Brownell
2007-08-21 7:24 ` Tony Lindgren
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=46C5CF29.2020601@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=felipebalbi@users.sourceforge.net \
--cc=linux-omap-open-source@linux.omap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox