From: Randy Dunlap <rdunlap@xenotime.net>
To: balbi@ti.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
akpm <akpm@linux-foundation.org>,
gregkh@suse.de, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-omap@vger.kernel.org
Subject: [PATCH -next v2] usb: fix dwc3 build when USB_GADGET_DWC3 is not enabled
Date: Tue, 23 Aug 2011 12:52:47 -0700 [thread overview]
Message-ID: <20110823125247.fbbf9636.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110823185235.GA11299@legolas.emea.dhcp.ti.com>
From: Randy Dunlap <rdunlap@xenotime.net>
Fix build error when CONFIG_USB_GADGET_DWC3 is not enabled:
ERROR: "dwc3_send_gadget_ep_cmd" [drivers/usb/dwc3/dwc3.ko] undefined!
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
drivers/usb/dwc3/gadget.h | 5 +++++
1 file changed, 5 insertions(+)
--- linux-next-20110823.orig/drivers/usb/dwc3/gadget.h
+++ linux-next-20110823/drivers/usb/dwc3/gadget.h
@@ -202,6 +202,11 @@ void dwc3_gadget_exit(struct dwc3 *dwc);
#else
static inline int dwc3_gadget_init(struct dwc3 *dwc) { return 0; }
static inline void dwc3_gadget_exit(struct dwc3 *dwc) { }
+static inline int dwc3_send_gadget_ep_cmd(struct dwc3 *dwc, unsigned ep,
+ unsigned cmd, struct dwc3_gadget_ep_cmd_params *params)
+{
+ return 0;
+}
#endif
void dwc3_gadget_giveback(struct dwc3_ep *dep, struct dwc3_request *req,
next prev parent reply other threads:[~2011-08-23 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 6:04 linux-next: Tree for Aug 23 Stephen Rothwell
2011-08-23 18:07 ` [PATCH -next] usb: fix dwc3 build when USB_GADGET_DWC3 is not enabled Randy Dunlap
2011-08-23 18:52 ` Felipe Balbi
2011-08-23 19:52 ` Randy Dunlap [this message]
2011-08-24 8:51 ` [PATCH -next v2] " Felipe Balbi
2011-08-23 18:22 ` [PATCH -next] usb: fix ipw.c build error, select USB_SERIAL_WWAN Randy Dunlap
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=20110823125247.fbbf9636.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=balbi@ti.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.