Documentation: hid: fix path to input bus definitions
Subsystems (3)
PATCH 1/4 Documentation: hid: fix path to input bus definitions
The UAPI header split failed to update the documentation here; fix things accordingly.
--- Documentation/hid/hidraw.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/hid/hidraw.txt +1 -1
@@ -81,7 +81,7 @@ of: BUS_HIL BUS_BLUETOOTH BUS_VIRTUAL -which are defined in linux/input.h. +which are defined in uapi/linux/input.h. HIDIOCGRAWNAME(len): Get Raw Name This ioctl returns a string containing the vendor and product strings of
Signature · 1 line
2.1.4
PATCH 2/4 Documentation: input: fix path to input code defnitions
The UAPI header split failed to update the documentation in input-programming.txt; fix things accordingly.
--- Documentation/input/input-programming.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/input/input-programming.txt +2 -2
@@ -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.
Signature · 1 line
2.1.4
PATCH 3/4 Documentation: admin-guide: fix path to input key definitions
In reply to Martin KepplingerThe UAPI header split failed to update the documentation here; fix things accordingly.
--- Documentation/admin-guide/sysrq.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/admin-guide/sysrq.rst +2 -1
@@ -212,7 +212,8 @@ I hit SysRq, but nothing seems to happen, what's wrong? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There are some keyboards that produce a different keycode for SysRq than the -pre-defined value of 99 (see ``KEY_SYSRQ`` in ``include/linux/input.h``), or +pre-defined value of 99 +(see ``KEY_SYSRQ`` in ``include/uapi/linux/input-event-codes.h``), or which don't have a SysRq key at all. In these cases, run ``showkey -s`` to find an appropriate scancode sequence, and use ``setkeycodes <sequence> 99`` to map this sequence to the usual SysRq code (e.g., ``setkeycodes e05b 99``). It's
Signature · 1 line
2.1.4
PATCH 4/4 Documentation: input: fix path to struct ff_effect's definition
In reply to Martin KepplingerThe UAPI header split failed to update the documentation here; fix things accordingly.
--- Documentation/input/ff.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/input/ff.txt +3 -3
@@ -106,9 +106,9 @@ allocate a new effect. Effects are file descriptor specific. -See <linux/input.h> for a description of the ff_effect struct. You should also -find help in a few sketches, contained in files shape.fig and interactive.fig. -You need xfig to visualize these files. +See <uapi/linux/input.h> for a description of the ff_effect struct. You should +also find help in a few sketches, contained in files shape.fig and +interactive.fig. You need xfig to visualize these files. 3.3 Removing an effect from the device ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Signature · 1 line
2.1.4
Quoted 2 lines · On Sun, 12 Mar 2017 12:54:21 +0100 Martin Kepplinger <[email protected]> wrote:
The UAPI header split failed to update the documentation here; fix things accordingly.
I've applied all four to the docs tree, thanks.
jon