Documentation: input: fix path to input code definitions
Subsystems (2)
PATCH 1/1 Documentation: input: fix path to input code definitions
Signed-off-by Martin Kepplinger <[email protected]>
--- Documentation/input/input.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/input/input.txt +2 -2
@@ -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
Signature · 1 line
2.1.4
Quoted 12 lines · On Thu, 9 Feb 2017 07:53:29 +0100 Martin Kepplinger <[email protected]> wrote:
Signed-off-by Martin Kepplinger <[email protected]>--- Documentation/input/input.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)Documentation/input/input.txt +0
-0@@ -279,10 +279,10 @@ struct input_event { 'time' is the timestamp, it returns the time at which the event happened.
Documentation/input/input.txt struct input_event { · line 288
Quoted 10 lines
Documentation/input/input.txt +2
-2Type 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