From: Greg KH <greg@kroah.com>
To: Todd Poynor <tpoynor@mvista.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Synchronous hotplug for kobjects
Date: Mon, 10 May 2004 21:19:59 +0000 [thread overview]
Message-ID: <20040510211959.GB10887@kroah.com> (raw)
In-Reply-To: <20040510204813.GA20691@dhcp193.mvista.com>
On Mon, May 10, 2004 at 01:48:13PM -0700, Todd Poynor wrote:
> As discussed recently, it's expected to be useful to generate
> synchronous hotplug events from the kobject subsystem in certain
> situations. This patch adds a kobject_hotplug_wait function that issues
> a synchronous call. The function should be used for appropriate actions
> that require synchronous semantics; please note many hotplug events
> would suffer severe performance degradation if issued synchronously, and
> one should exercise caution in choosing to use this function.
How about I wait until someone really needs this function before adding
it? Or do you have a patch that does need it?
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next parent reply other threads:[~2004-05-10 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040510204813.GA20691@dhcp193.mvista.com>
2004-05-10 21:19 ` Greg KH [this message]
2004-05-11 1:09 ` [PATCH] Synchronous hotplug for kobjects Todd Poynor
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=20040510211959.GB10887@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tpoynor@mvista.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;
as well as URLs for NNTP newsgroup(s).