From: Greg KH <greg@kroah.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] kobject/hotplug split
Date: Wed, 23 Mar 2005 14:18:34 -0800 [thread overview]
Message-ID: <20050323221834.GA5968@kroah.com> (raw)
In-Reply-To: <20050318040000.GA475@vrfy.org>
On Fri, Mar 18, 2005 at 05:00:00AM +0100, Kay Sievers wrote:
> This splits the implicit generation of hotplug events from
> kobject_add() and kobject_del(), to give the driver core
> control over the time the event is created.
>
> The kobject_register() and unregister functions still have the same
> behavior and emit the events by themselves.
>
> The class, block and device core is changed now to emit the hotplug
> event _after_ the "dev" file, the "device" symlink and the default
> attributes are created. This will save udev from spinning in a stat() loop
> to wait for the files to appear, which is expensive if we have a lot of
> concurrent events.
Thanks for splitting this up. I've applied all 6 to my trees now.
greg k-h
prev parent reply other threads:[~2005-03-23 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 4:00 [PATCH 0/6] kobject/hotplug split Kay Sievers
2005-03-23 22:18 ` Greg KH [this message]
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=20050323221834.GA5968@kroah.com \
--to=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--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