From: Hannes Reinecke <hare@suse.de>
To: dtor_core@ameritech.net
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [PATCH 2/2] Remove input_call_hotplug
Date: Wed, 19 Jan 2005 10:59:30 +0100 [thread overview]
Message-ID: <41EE2F82.3080401@suse.de> (raw)
In-Reply-To: <d120d50005011807566ee35b2b@mail.gmail.com>
Dmitry Torokhov wrote:
> Hi,
>
> On Tue, 18 Jan 2005 15:59:35 +0100, Hannes Reinecke <hare@suse.de> wrote:
>
>>Implement proper class names for input drivers.
>>
>
>
> This patch probably should probably use atomic_inc in case we ever
> have non-serialized probe functions.
>
True.
> But the real question is whether we really need class devices have
> unique names or we could do with inputX thus leaving individual
> drivers intact and only modifying the input core. As far as I
> understand userspace should be concerned only with device
> capabilities, not particular name, besides, it gets PRODUCT string
> which has all needed data encoded.
>
Indeed. What about using 'phys' (with all '/' replaced by '-') as the
class_id? This way we'll retain compability with /proc/bus/input/devices
and do not have to touch every single driver.
Better idea?
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
next prev parent reply other threads:[~2005-01-19 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 14:59 [PATCH 2/2] Remove input_call_hotplug Hannes Reinecke
2005-01-18 15:56 ` Dmitry Torokhov
2005-01-19 9:59 ` Hannes Reinecke [this message]
2005-01-19 14:05 ` Dmitry Torokhov
2005-01-19 14:16 ` Hannes Reinecke
2005-01-19 14:44 ` Dmitry Torokhov
2005-01-19 14:56 ` Hannes Reinecke
2005-01-19 15:49 ` Vojtech Pavlik
2005-01-19 15:50 ` Hannes Reinecke
2005-01-19 16:53 ` Vojtech Pavlik
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=41EE2F82.3080401@suse.de \
--to=hare@suse.de \
--cc=dtor_core@ameritech.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.