diff options
| author | Martin Kepplinger <martink@posteo.de> | 2017-03-12 12:54:23 +0100 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2017-03-13 17:15:30 -0600 |
| commit | 30e010f64a9da9928dc3df205b96155e68c2eff1 (patch) | |
| tree | 0880e0eadd2152df46254cd02c288cab819de16d | |
| parent | 28a5c9648bcb8e55ee6b9ff8a707c5c654f3b633 (diff) | |
| download | linux-30e010f64a9da9928dc3df205b96155e68c2eff1.tar.bz2 | |
Documentation: admin-guide: fix path to input key definitions
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>
| -rw-r--r-- | Documentation/admin-guide/sysrq.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/admin-guide/sysrq.rst b/Documentation/admin-guide/sysrq.rst index d1712ea2d314..7b9035c01a2e 100644 --- a/Documentation/admin-guide/sysrq.rst +++ b/Documentation/admin-guide/sysrq.rst @@ -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 |