mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Alexander Holler <holler@ahsoftware.de>
Cc: balbi@ti.com, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: musb as module broken in 2.6.38
Date: Wed, 16 Mar 2011 11:03:28 +0200	[thread overview]
Message-ID: <20110316090327.GA2325@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <4D8018A9.6000800@ahsoftware.de>

Hi,

On Wed, Mar 16, 2011 at 02:55:53AM +0100, Alexander Holler wrote:
> in commit dc09886bfa781e2b442301116c18199519e36f0f the name of the
> platform-driver was splitted and musb-omap2430 is used for several
> boards (arch/arm/mach-omap2/usb-musb.c).
> 
> But musb_hdrc still uses musb-hdrc as name when
> platform_driver_probe() is called. The result is that loading the
> driver (when build as a module) doesn't work anymore (it doesn't find
> the platform-device).
> 
> Do I miss something or was something forgotten when the glue-layers
> for musb got introduced?
> 
> (The driver still works when linked into the kernel, but is
> disfunctional when build as a module.)

Send me the output you get on console and a snippet of the .config with
the MUSB section.

-- 
balbi

  reply	other threads:[~2011-03-16  9:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16  1:55 Alexander Holler
2011-03-16  9:03 ` Felipe Balbi [this message]
2011-03-16  9:47   ` Alexander Holler
2011-03-16  9:55     ` Felipe Balbi
2011-03-16 10:17       ` Alexander Holler
2011-03-16 10:24         ` Felipe Balbi
2011-03-16 10:30           ` Alexander Holler
2011-03-16 10:38             ` Felipe Balbi
2011-03-16 10:43               ` Alexander Holler
2011-03-16 10:48                 ` Felipe Balbi
2011-03-16 11:21                   ` Alexander Holler
2011-03-16 12:51                     ` Felipe Balbi

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=20110316090327.GA2325@legolas.emea.dhcp.ti.com \
    --to=balbi@ti.com \
    --cc=holler@ahsoftware.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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

all inboxes | Powered by JetHome®