From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: big cleanup of internal udev api
Date: Mon, 18 Oct 2004 18:15:49 +0000 [thread overview]
Message-ID: <20041018181548.GA23316@kroah.com> (raw)
In-Reply-To: <20041018144230.GB6821@vrfy.org>
On Mon, Oct 18, 2004 at 04:42:30PM +0200, Kay Sievers wrote:
> Here is the first patch to cleanup the internal processing of the
> various stages of an udev event. It should not change any behavior,
> but if your system depends on udev, please always test it before reboot :)
>
> We pass only one generic structure around between add, remove,
> namedev, db and dev_d handling and make all relevant data available
> to all internal stages. All udev structures are renamed to "udev".
>
> We replace the fake parameter by a flag in the udev structure.
>
> We open the class device in the main binaries and not in udev_add, to
> make it possible to use libsysfs for udevstart directory crawling.
>
> The last sleep parameters are removed.
Nice cleanup, thanks for doing this.
Applied,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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:[~2004-10-18 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 14:42 big cleanup of internal udev api Kay Sievers
2004-10-18 18:15 ` 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=20041018181548.GA23316@kroah.com \
--to=greg@kroah.com \
--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).