From: Mark Lord <kernel@teksavvy.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [git pull] Input updates for 3.5-rc0
Date: Fri, 25 May 2012 15:05:00 -0400 [thread overview]
Message-ID: <4FBFD7DC.9070604@teksavvy.com> (raw)
In-Reply-To: <20120524195851.GA15306@core.coreip.homeip.net>
On 12-05-24 03:58 PM, Dmitry Torokhov wrote:
>
> On the topic of naming - nobody cares what input devices are called as
> long as they are unique. Userspace does not work with input devices
> directly (there is no API), they are working with iterfaces (such as
> evdev) that have their own interfaces and names.
I regularly work with input devices from userspace,
using the "lsinput" "xinput", and "input-kbd" commands (among others)
from various shell scripts.
So I guess that makes me one of those anonymous "nobody" types
who "don't care" about it.
Usually the device naming I see there makes some kind of sense.
next prev parent reply other threads:[~2012-05-25 19:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 8:32 [git pull] Input updates for 3.5-rc0 Dmitry Torokhov
2012-05-24 17:33 ` Linus Torvalds
2012-05-24 18:01 ` Dmitry Torokhov
2012-05-24 18:21 ` Linus Torvalds
2012-05-24 19:58 ` Dmitry Torokhov
2012-05-24 20:11 ` Linus Torvalds
2012-05-24 20:36 ` Dmitry Torokhov
2012-05-24 20:48 ` Linus Torvalds
2012-05-24 20:59 ` Dmitry Torokhov
2012-05-24 21:07 ` Linus Torvalds
2012-05-24 21:38 ` Dmitry Torokhov
2012-05-24 21:56 ` Linus Torvalds
2012-05-24 21:44 ` Linus Torvalds
2012-05-24 21:56 ` Dmitry Torokhov
2012-05-24 21:59 ` Linus Torvalds
2012-05-24 22:01 ` Greg Kroah-Hartman
2012-05-24 22:05 ` Linus Torvalds
2012-05-25 1:39 ` Greg Kroah-Hartman
2012-05-25 19:05 ` Mark Lord [this message]
2012-05-24 21:26 ` Greg Kroah-Hartman
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=4FBFD7DC.9070604@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).