From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Best practice for loading platform modules
Date: Wed, 29 Apr 2009 20:18:21 +0000 [thread overview]
Message-ID: <20090429201821.GA20814@kroah.com> (raw)
In-Reply-To: <c4aed99f0904291105u1d4c0081qe91969a3ada64c96@mail.gmail.com>
On Wed, Apr 29, 2009 at 03:53:53PM -0400, Chris Hallinan wrote:
> On Wed, Apr 29, 2009 at 3:46 PM, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > On Wed, Apr 29, 2009 at 21:35, Chris Hallinan <challinan@gmail.com> wrote:
> >
> >> Erm, I am the distro maintainer!
Heh, my condolences...
You should possibly post from your company email address if you expect
us to know this, gmail.com doesn't exactly specify much :)
> >> I tried just today w/ 2.6.29. The
> >> problem seems like a mismatch. Kernel passes "platform:musb_hdrc".
> >> Udev receives and passes same to modprobe. The answer I'm seeking is
> >> "what is the correct/proper approach?" Should I seek to modify the
> >> kernel and remove the "platform:" prefix, or should I seek a
> >> modification to modprobe to be able to understand and strip off the
> >> "platform:" prefix? Or should udev have a construct/rules syntax to
> >> strip the "platform:" prefix?
> >
> > The module itself, if that's still needed.
> >
>
> OK, the light bulb just came on!
>
> Thanks, Kay, and Greg for hanging in there with me. I added
> MODULE_ALIAS("platform:musb_hdrc) to musb_core.c, and all works as advertised.
But that alias is already there, it was added in the 2.6.27-rc kernel,
in commit 550a7375.
So I'm confused as to why 2.6.29 would not work properly for you.
thanks,
greg k-h
next prev parent reply other threads:[~2009-04-29 20:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 18:05 Best practice for loading platform modules Chris Hallinan
2009-04-29 18:11 ` Greg KH
2009-04-29 18:12 ` Greg KH
2009-04-29 18:31 ` Chris Hallinan
2009-04-29 18:44 ` Greg KH
2009-04-29 19:15 ` Chris Hallinan
2009-04-29 19:25 ` Greg KH
2009-04-29 19:33 ` Kay Sievers
2009-04-29 19:35 ` Chris Hallinan
2009-04-29 19:46 ` Kay Sievers
2009-04-29 19:53 ` Chris Hallinan
2009-04-29 20:18 ` Greg KH [this message]
2009-04-30 0:48 ` Chris Hallinan
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=20090429201821.GA20814@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).