From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks
Date: Sun, 16 May 2010 16:04:25 +0000 [thread overview]
Message-ID: <20100516160425.GA11444@kroah.com> (raw)
In-Reply-To: <20100513134742.GB1768@piware.de>
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?
curious,
greg k-h
next prev parent reply other threads:[~2010-05-16 16:04 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 [this message]
2010-05-17 11:10 ` Scott James Remnant
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=20100516160425.GA11444@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).