linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.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:11:21 +0000	[thread overview]
Message-ID: <d120d5000509210911615865a5@mail.gmail.com> (raw)
In-Reply-To: <1127270286.10585.14.camel@localhost.localdomain>

On 9/21/05, Greg KH <greg@kroah.com> wrote:
> 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?
>

Well, no ;) I was trying to make them separable. I will resping the
dynamic allocation patches, but I would also like to get sysfs part
going - there are bunch of locking issues (or rather absence of
locking ;) ) in input core and I would like to fix it but I don't want
to redo it later to account for sysfs rules. That's why I am pushing
to get some kind of sysfs resolution. Again, that "name override"
would go away later, I do not propose it as a permanant solution.

--
Dmitry


-------------------------------------------------------
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

  parent reply	other threads:[~2005-09-21 16:11 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
2005-09-21 16:11 ` Dmitry Torokhov [this message]
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=d120d5000509210911615865a5@mail.gmail.com \
    --to=dmitry.torokhov@gmail.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).