public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Vojtech Pawlik <vojtech@suse.cz>
Subject: Re: [PATCH 0/2] Remove input_call_hotplug
Date: Tue, 18 Jan 2005 13:30:02 -0800	[thread overview]
Message-ID: <20050118213002.GA17004@kroah.com> (raw)
In-Reply-To: <41ED23A3.5020404@suse.de>

On Tue, Jan 18, 2005 at 03:56:35PM +0100, Hannes Reinecke wrote:
> Hi all,
> 
> the input subsystem is using call_usermodehelper directly, which breaks 
> all sorts of assertions especially when using udev.
> And it's definitely going to fail once someone is trying to use netlink 
> messages for hotplug event delivery.
> 
> To remedy this I've implemented a new sysfs class 'input_device' which 
> is a representation of 'struct input_dev'. So each device listed in 
> '/proc/bus/input/devices' gets a class device associated with it.
> And we'll get proper hotplug events for each input_device which can be 
> handled by udev accordingly.

Hm, why another input class?  We already have /sys/class/input, which we
get hotplug events for.  We also have the individual input device
hotplug events, which is what I think we really want here, right?

Hm, in looking at the code some more, I think just adding a struct
device to the struct input_device would work.  You will have to refactor
out the fact that there is a pointer to a struct device in there (that
will just become the parent pointer to the input_dev's struct device).
If you do that, you can also drop a few of the fields in struct
input_dev.

That would solve all of the userspace issues your patch causes (hotplug
events would come out with the same type as before) and finally the
input subsystem would be part of the driver model properly :)

But yes, it will take more work than your patch, sorry.

thanks,

greg k-h

  reply	other threads:[~2005-01-18 21:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18 14:56 [PATCH 0/2] Remove input_call_hotplug Hannes Reinecke
2005-01-18 21:30 ` Greg KH [this message]
2005-01-18 21:49   ` Dmitry Torokhov
2005-01-18 21:58     ` Greg KH
2005-01-18 22:20       ` Dmitry Torokhov
2005-01-19  1:31         ` Greg KH
2005-01-19 11:56           ` Hannes Reinecke
2005-01-19 14:30             ` Dmitry Torokhov
2005-01-19 21:39               ` 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=20050118213002.GA17004@kroah.com \
    --to=greg@kroah.com \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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