From: tony@atomide.com
To: David Brownell <david-b@pacbell.net>
Cc: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
linux-omap-open-source@linux.omap.com
Subject: Re: Undefined usb_disconnect
Date: Tue, 4 Jul 2006 01:20:38 -0700 [thread overview]
Message-ID: <20060704082029.GB4962@atomide.com> (raw)
In-Reply-To: <200605270843.54940.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [060527 08:44]:
> On Friday 26 May 2006 11:38 pm, Dirk Behme wrote:
> > Hi,
> >
> > with recent git I still get
> >
> > WARNING: "usb_disconnect" [drivers/usb/host/ohci-hcd.ko]
> > undefined!
>
> Try the attached patch instead ... it fixes some other glitches
> in the OMAP bus glue, as well as those.
>
> - Dave
>
>
>
>
> Various fixes for the OHCI OMAP glue:
>
> - Properly use the usbcore HCD lifecycle entry points
>
> - Remove calls to non-exported usbcore routines.
>
> - Stop inappropriate export of some bus glue calls
>
> Plus remove some extra whitespace.
<snip>
I'll push this today slightly updated. Sorry, I should have pushed
this earlier.
Dave, I assume you will eventually send this upstream through your
USB channels so I did not tag this as a ARM: OMAP: patch.
Regards,
Tony
next prev parent reply other threads:[~2006-07-04 8:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 15:44 [PATCH] ARM: OMAP: Fix tlv320aic23.c Dirk Behme
2006-05-03 12:56 ` Tony Lindgren
2006-05-03 18:41 ` Dirk Behme
2006-05-04 14:51 ` David Brownell
2006-05-04 16:08 ` Undefined usb_disconnect, was " Dirk Behme
2006-05-04 16:32 ` David Brownell
2006-05-05 4:50 ` Undefined usb_disconnect Dirk Behme
2006-05-05 8:08 ` Hiroshi DOYU
2006-05-27 6:38 ` Dirk Behme
2006-05-27 15:43 ` David Brownell
2006-05-28 13:21 ` Dirk Behme
2006-05-28 16:17 ` David Brownell
2006-07-04 8:20 ` tony [this message]
2006-05-03 19:42 ` [PATCH] ARM: OMAP: Fix tlv320aic23.c lamikr
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=20060704082029.GB4962@atomide.com \
--to=tony@atomide.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=david-b@pacbell.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