From: Greg KH <greg@kroah.com>
To: John Zielinski <grim@undead.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] sysfs kobject that doesn't trigger hotplug events
Date: Tue, 18 May 2004 20:34:39 -0700 [thread overview]
Message-ID: <20040519033439.GA8160@kroah.com> (raw)
In-Reply-To: <40AAC26C.2080803@undead.cc>
On Tue, May 18, 2004 at 10:11:56PM -0400, John Zielinski wrote:
>
> Looking through the kobject.c code I noticed that this would create a
> lot of hotplug events which would burn up a bit of processor time.
> These events are not necessary as these are not device kobjects. I've
> enclosed a patch to my solution for this. I'd like to know if there are
> any side effects with this method.
Your patch is not needed at all. Please read the first comment in the
kobject_hotplug() function to see how to prevent kobjects from creating
hotplug events.
thanks,
greg k-h
next prev parent reply other threads:[~2004-05-19 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 2:11 [RFC] sysfs kobject that doesn't trigger hotplug events John Zielinski
2004-05-19 3:18 ` Dmitry Torokhov
2004-05-21 1:19 ` John Zielinski
2004-05-19 3:34 ` Greg KH [this message]
2004-05-19 4:43 ` John Zielinski
2004-05-19 5:16 ` Greg KH
2004-05-22 1:38 ` John Zielinski
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=20040519033439.GA8160@kroah.com \
--to=greg@kroah.com \
--cc=grim@undead.cc \
--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