From: Greg KH <greg@kroah.com>
To: Jamey Hicks <jamey.hicks@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: recursive call to platform_device_register deadlocks
Date: Sat, 18 Jun 2005 22:59:24 -0700 [thread overview]
Message-ID: <20050619055924.GA14674@kroah.com> (raw)
In-Reply-To: <42B43226.20703@hp.com>
On Sat, Jun 18, 2005 at 10:39:34AM -0400, Jamey Hicks wrote:
>
> We could restructure the toplevel driver so that it does not call
> platform_device inside its probe function. An alternative would be to
> add a pointer to a vector of subdevices to platform_device and have it
> register the subdevices after it has probed the toplevel device. Do you
> have any recommendations?
Use the -mm kernel, this should be allowed in that release, due to a
rework of the driver core logic in this area. Can you test this out and
verify this?
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-19 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 14:39 recursive call to platform_device_register deadlocks Jamey Hicks
2005-06-19 5:59 ` Greg KH [this message]
2005-06-20 13:26 ` Jamey Hicks
2005-06-21 13:55 ` Jamey Hicks
2005-06-21 7:43 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2005-06-18 16:06 David Brownell
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=20050619055924.GA14674@kroah.com \
--to=greg@kroah.com \
--cc=jamey.hicks@hp.com \
--cc=linux-kernel@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