linux-kernel - Re: [PATCH] Documentation: input: fix path to input code definitions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170212151851.76f2aa12@lwn.net>
Date:   Sun, 12 Feb 2017 15:18:51 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Martin Kepplinger <martink@...teo.de>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: input: fix path to input code
 definitions

On Thu,  9 Feb 2017 07:53:29 +0100
Martin Kepplinger <martink@...teo.de> wrote:

> Signed-off-by: Martin Kepplinger <martink@...teo.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