Documentation: admin-guide: fix path to input key definitions
authorMartin Kepplinger <martink@posteo.de>
Sun, 12 Mar 2017 11:54:23 +0000 (12:54 +0100)
committerJonathan Corbet <corbet@lwn.net>
Mon, 13 Mar 2017 23:15:30 +0000 (17:15 -0600)
The UAPI header split failed to update the documentation here; fix things
accordingly.

Signed-off-by: Martin Kepplinger <martink@posteo.de>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Documentation/admin-guide/sysrq.rst

index d1712ea2d314da0f0405ec00f5ad410f1014b2db..7b9035c01a2e1c01d68336d891402f54362cdb13 100644 (file)
@@ -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