From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: The case of udev and the missing /dev/input/mice
Date: Wed, 21 Sep 2005 16:00:49 +0000 [thread overview]
Message-ID: <20050921160049.GA7959@kroah.com> (raw)
In-Reply-To: <1127270286.10585.14.camel@localhost.localdomain>
On Wed, Sep 21, 2005 at 08:49:43AM -0700, Greg KH wrote:
> > Greg, would you accept a patch that would allow a class override its
> > subsustem as far as hotplug is concerned? This way "input_dev" class
> > would set its name to "input" allowing using existing setups.
Actually, it would be nice if you could respin your patches that convert
all of the input devices to be dynamically created. That would work
just fine today with no sysfs changes, right?
That way, any future changes we do would be much smaller, and could be
done on top of your patchset.
Or am I missing some deep dependencies in your patchset?
thanks,
greg k-h
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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
next prev parent reply other threads:[~2005-09-21 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 2:38 The case of udev and the missing /dev/input/mice Scott James Remnant
2005-09-21 9:51 ` Kay Sievers
2005-09-21 11:19 ` Olivier Blin
2005-09-21 12:47 ` Greg KH
2005-09-21 12:53 ` Scott James Remnant
2005-09-21 15:33 ` Dmitry Torokhov
2005-09-21 15:49 ` Greg KH
2005-09-21 16:00 ` Greg KH [this message]
2005-09-21 16:11 ` Dmitry Torokhov
2005-09-21 16:33 ` Greg KH
2005-09-21 16:46 ` Dmitry Torokhov
2005-09-21 17:01 ` Greg KH
2005-09-21 17:12 ` Dmitry Torokhov
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=20050921160049.GA7959@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).