From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: CONFIG_HOTPLUG obsolete in 2.6.15+
Date: Sun, 29 Jan 2006 14:33:11 +0000 [thread overview]
Message-ID: <20060129143311.GA22154@vrfy.org> (raw)
In-Reply-To: <200601291615.17396.arvidjaar@mail.ru>
On Sun, Jan 29, 2006 at 04:15:13PM +0300, Andrey Borzenkov wrote:
> Do I understand it correctly that in current kernel CONFIG_HOTPLUG can be
> replaced by CONFIG_KOBJECT_UEVENT? Assuming current udev of course.
No, CONFIG_KOBJECT_UEVENT does not exist anymore and CONFIG_HOTPLUG is
only available for EMBEDDED. Nothing left in that area to break your system.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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
prev parent reply other threads:[~2006-01-29 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 13:15 CONFIG_HOTPLUG obsolete in 2.6.15+ Andrey Borzenkov
2006-01-29 14:33 ` Kay Sievers [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=20060129143311.GA22154@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).