From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Peter Hutterer <peter.hutterer@who-t.net>,
Nikolai Kondrashov <spbnick@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Bagwell <chris@cnpbagwell.com>
Subject: Re: [PATCH v4] Documentation: Add evdev type and code definitions
Date: Wed, 6 Apr 2011 15:07:01 -0700 [thread overview]
Message-ID: <20110406220701.GA11611@core.coreip.homeip.net> (raw)
In-Reply-To: <1302121172-16703-1-git-send-email-chase.douglas@canonical.com>
Hi Chase,
On Wed, Apr 06, 2011 at 04:19:31PM -0400, Chase Douglas wrote:
> This commit adds the file Documentation/input/evdev-codes.txt.
>
> Cc: Henrik Rydberg <rydberg@euromail.se>
> Cc: Peter Hutterer <peter.hutterer@who-t.net>
> Cc: Nikolai Kondrashov <spbnick@gmail.com>
> Cc: linux-input@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Acked-by: Henrik Rydberg <rydberg@euromail.se>
> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
> Signed-off-by: Chris Bagwell <chris@cnpbagwell.com>
Thank you very much for doing this. I am very happy with the state of
document at the moment and I want to apply it and get in .39.
The only 2 changes I'd like (I'll do them on my side) is renaming the
file from evdev-codes to event-codes and evdev protocol to input
protocol since the data applicable not only to evdev but to entire input
core.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-04-06 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 20:19 [PATCH v4] Documentation: Add evdev type and code definitions Chase Douglas
2011-04-06 20:19 ` [PATCH v4] Documentation: Add evdev type and code definitions (changes) Chase Douglas
2011-04-06 22:07 ` Dmitry Torokhov [this message]
2011-04-07 0:48 ` [PATCH v4] Documentation: Add evdev type and code definitions Peter Hutterer
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=20110406220701.GA11611@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=chris@cnpbagwell.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=rydberg@euromail.se \
--cc=spbnick@gmail.com \
/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).