From: Scott James Remnant <scott@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks
Date: Mon, 17 May 2010 11:10:06 +0000 [thread overview]
Message-ID: <1274094606.1672.0.camel@quest> (raw)
In-Reply-To: <20100513134742.GB1768@piware.de>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On Sun, 2010-05-16 at 09:04 -0700, Greg KH wrote:
> On Sun, May 16, 2010 at 12:22:47PM +0100, Scott James Remnant wrote:
> > I consider myself an active member of udev upstream, and I think we've
> > taken a wrong turn with the design and implementation.
>
> What specifically do you mean by this?
>
> Is the current libudev not a good design for your needs? What should it
> be instead?
>
Actually, quite the opposite! I think that libudev is a great design.
I think that the wrong turn is that we rely on a massive "cold plug"
phase during boot, and we rely on probing every single piece of hardware
during that phase or on later insertion - whether or not anything on the
system actually cares about the result.
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-17 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 13:47 udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks rules Martin Pitt
2010-05-13 14:06 ` udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks Lennart Poettering
2010-05-16 11:22 ` Scott James Remnant
2010-05-16 16:04 ` Greg KH
2010-05-17 11:10 ` Scott James Remnant [this message]
2010-05-17 16:14 ` Greg KH
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=1274094606.1672.0.camel@quest \
--to=scott@ubuntu.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).