From: Martin Kepplinger <martink@posteo.de>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Kepplinger <martink@posteo.de>
Subject: [PATCH 2/4] Documentation: input: fix path to input code defnitions
Date: Sun, 12 Mar 2017 12:54:22 +0100 [thread overview]
Message-ID: <1489319664-29651-2-git-send-email-martink@posteo.de> (raw)
In-Reply-To: <1489319664-29651-1-git-send-email-martink@posteo.de>
The UAPI header split failed to update the documentation in
input-programming.txt; fix things accordingly.
Signed-off-by: Martin Kepplinger <martink@posteo.de>
---
Documentation/input/input-programming.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/input/input-programming.txt b/Documentation/input/input-programming.txt
index 7f8b9d9..c3b940b 100644
--- a/Documentation/input/input-programming.txt
+++ b/Documentation/input/input-programming.txt
@@ -174,8 +174,8 @@ It's reported to the input system via:
input_report_key(struct input_dev *dev, int code, int value)
-See linux/input.h for the allowable values of code (from 0 to KEY_MAX).
-Value is interpreted as a truth value, ie any nonzero value means key
+See uapi/linux/input-event-codes.h for the allowable values of code (from 0 to
+KEY_MAX). Value is interpreted as a truth value, ie any nonzero value means key
pressed, zero value means key released. The input code generates events only
in case the value is different from before.
--
2.1.4
next prev parent reply other threads:[~2017-03-12 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 11:54 [PATCH 1/4] Documentation: hid: fix path to input bus definitions Martin Kepplinger
2017-03-12 11:54 ` Martin Kepplinger [this message]
2017-03-12 11:54 ` [PATCH 3/4] Documentation: admin-guide: fix path to input key definitions Martin Kepplinger
2017-03-12 11:54 ` [PATCH 4/4] Documentation: input: fix path to struct ff_effect's definition Martin Kepplinger
2017-03-13 23:19 ` [PATCH 1/4] Documentation: hid: fix path to input bus definitions Jonathan Corbet
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=1489319664-29651-2-git-send-email-martink@posteo.de \
--to=martink@posteo.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®