From: Jonathan Corbet <corbet@lwn.net>
To: Martin Kepplinger <martink@posteo.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: input: fix path to input code definitions
Date: Sun, 12 Feb 2017 15:18:51 -0700 [thread overview]
Message-ID: <20170212151851.76f2aa12@lwn.net> (raw)
In-Reply-To: <1486623209-24678-1-git-send-email-martink@posteo.de>
On Thu, 9 Feb 2017 07:53:29 +0100
Martin Kepplinger <martink@posteo.de> wrote:
> Signed-off-by: Martin Kepplinger <martink@posteo.de>
> ---
> Documentation/input/input.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/input/input.txt b/Documentation/input/input.txt
> index 0acfddb..7ebce10 100644
> --- a/Documentation/input/input.txt
> +++ b/Documentation/input/input.txt
> @@ -279,10 +279,10 @@ struct input_event {
>
> 'time' is the timestamp, it returns the time at which the event happened.
> Type is for example EV_REL for relative moment, EV_KEY for a keypress or
> -release. More types are defined in include/linux/input.h.
> +release. More types are defined in include/uapi/linux/input-event-codes.h.
>
> 'code' is event code, for example REL_X or KEY_BACKSPACE, again a complete
> -list is in include/linux/input.h.
> +list is in include/uapi/linux/input-event-codes.h.
>
> 'value' is the value the event carries. Either a relative change for
> EV_REL, absolute new value for EV_ABS (joysticks ...), or 0 for EV_KEY for
Applied to the docs tree, thanks. In the future, though, a proper
changelog text describing the change would be appreciated.
Thanks,
jon
prev parent reply other threads:[~2017-02-12 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 6:53 [PATCH] Documentation: input: fix path to input code definitions Martin Kepplinger
2017-02-12 22:18 ` Jonathan Corbet [this message]
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=20170212151851.76f2aa12@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
/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