From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: linux-os@analogic.com
Cc: Alan Stern <stern@rowland.harvard.edu>,
Kernel development list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: Locking changes to the driver-model core
Date: Wed, 16 Mar 2005 17:19:29 -0500 [thread overview]
Message-ID: <d120d50005031614194a3bc41a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503161602530.6525@chaos.analogic.com>
On Wed, 16 Mar 2005 16:10:11 -0500 (EST), linux-os
<linux-os@analogic.com> wrote:
>
> Thought experiment:
> Suppose you had a kernel-thread whos duty it was to handle the
> shutdown and restarting of devices on such busses. Since it
> is the only thing that would touch such code, wouldn't things
> be a lot simpler and not subject to deadlocks?
>
You'd still have to mind devices that were added/removed from
probe/remove handlers while walking lists.
--
Dmitry
next prev parent reply other threads:[~2005-03-16 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 20:58 Locking changes to the driver-model core Alan Stern
2005-03-16 21:10 ` linux-os
2005-03-16 21:36 ` Alan Stern
2005-03-16 22:19 ` Dmitry Torokhov [this message]
2005-03-19 7:01 ` Greg KH
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=d120d50005031614194a3bc41a@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=mochel@digitalimplant.org \
--cc=stern@rowland.harvard.edu \
/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