Skip to contentSkip to conversation

Documentation: Update path to sysrq.txt

PATCH Applied Krzysztof Kozlowski 3 participants 3 messages Feb 24, 2017 – Mar 3, 2017

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Documentation: Update path to sysrq.txt

Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the sysrq.txt leaving old paths in the kernel docs.

---
 Documentation/media/v4l-drivers/bttv.rst          | 2 +-
 Documentation/s390/Debugging390.txt               | 2 +-
 Documentation/sysctl/kernel.txt                   | 2 +-
 Documentation/virtual/uml/UserModeLinux-HOWTO.txt | 6 +++---
 4 files changed, 6 insertions(+), 6 deletions(-)
Documentation/media/v4l-drivers/bttv.rst +1 -1
index bc63b12efafd..195ccaac2816 100644
@@ -312,7 +312,7 @@ information out of a register+stack dump printed by the kernel on
 protection faults (so-called "kernel oops").
 
 If you run into some kind of deadlock, you can try to dump a call trace
-for each process using sysrq-t (see Documentation/sysrq.txt).
+for each process using sysrq-t (see Documentation/admin-guide/sysrq.rst).
 This way it is possible to figure where *exactly* some process in "D"
 state is stuck.
 
Documentation/s390/Debugging390.txt +1 -1
index 3df8babcdc41..5ae7f868a007 100644
@@ -2116,7 +2116,7 @@ The sysrq key reading is very picky ( I have to type the keys in an
 This is particularly useful for syncing disks unmounting & rebooting
 if the machine gets partially hung.
 
-Read Documentation/sysrq.txt for more info
+Read Documentation/admin-guide/sysrq.rst for more info
 
 References:
 ===========
Documentation/sysctl/kernel.txt +1 -1
index a32b4b748644..bac23c198360 100644
@@ -85,7 +85,7 @@ show up in /proc/sys/kernel:
 - softlockup_all_cpu_backtrace
 - soft_watchdog
 - stop-a                      [ SPARC only ]
-- sysrq                       ==> Documentation/sysrq.txt
+- sysrq                       ==> Documentation/admin-guide/sysrq.rst
 - sysctl_writes_strict
 - tainted
 - threads-max
Documentation/virtual/uml/UserModeLinux-HOWTO.txt +3 -3
index f4099ca6b483..87b80f589e1c 100644
@@ -2401,9 +2401,9 @@
 
   This takes one argument, which is a single letter.  It calls the
   generic kernel's SysRq driver, which does whatever is called for by
-  that argument.  See the SysRq documentation in Documentation/sysrq.txt
-  in your favorite kernel tree to see what letters are valid and what
-  they do.
+  that argument.  See the SysRq documentation in
+  Documentation/admin-guide/sysrq.rst in your favorite kernel tree to
+  see what letters are valid and what they do.
 
 
 
Signature · 1 line
2.9.3
Reviewed-by on v1 1/1
#1 lore raw

Em Fri, 24 Feb 2017 10:42:14 +0200
Krzysztof Kozlowski <[email protected]> escreveu:

Quoted 4 lines

Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the sysrq.txt leaving old paths in the kernel docs.

Quoted 53 lines
---
 Documentation/media/v4l-drivers/bttv.rst          | 2 +-
 Documentation/s390/Debugging390.txt               | 2 +-
 Documentation/sysctl/kernel.txt                   | 2 +-
 Documentation/virtual/uml/UserModeLinux-HOWTO.txt | 6 +++---
 4 files changed, 6 insertions(+), 6 deletions(-)
Documentation/media/v4l-drivers/bttv.rst +1 -1
index bc63b12efafd..195ccaac2816 100644
@@ -312,7 +312,7 @@ information out of a register+stack dump printed by the kernel on
 protection faults (so-called "kernel oops").
 
 If you run into some kind of deadlock, you can try to dump a call trace
-for each process using sysrq-t (see Documentation/sysrq.txt).
+for each process using sysrq-t (see Documentation/admin-guide/sysrq.rst).
 This way it is possible to figure where *exactly* some process in "D"
 state is stuck.
 
Documentation/s390/Debugging390.txt +1 -1
index 3df8babcdc41..5ae7f868a007 100644
@@ -2116,7 +2116,7 @@ The sysrq key reading is very picky ( I have to type the keys in an
 This is particularly useful for syncing disks unmounting & rebooting
 if the machine gets partially hung.
 
-Read Documentation/sysrq.txt for more info
+Read Documentation/admin-guide/sysrq.rst for more info
 
 References:
 ===========
Documentation/sysctl/kernel.txt +1 -1
index a32b4b748644..bac23c198360 100644
@@ -85,7 +85,7 @@ show up in /proc/sys/kernel:
 - softlockup_all_cpu_backtrace
 - soft_watchdog
 - stop-a                      [ SPARC only ]
-- sysrq                       ==> Documentation/sysrq.txt
+- sysrq                       ==> Documentation/admin-guide/sysrq.rst
 - sysctl_writes_strict
 - tainted
 - threads-max
Documentation/virtual/uml/UserModeLinux-HOWTO.txt +0 -0
index f4099ca6b483..87b80f589e1c 100644
@@ -2401,9 +2401,9 @@
 
   This takes one argument, which is a single letter.  It calls the

Documentation/virtual/uml/UserModeLinux-HOWTO.txt line 2409

Quoted 10 lines
Documentation/virtual/uml/UserModeLinux-HOWTO.txt +3 -3
   generic kernel's SysRq driver, which does whatever is called for by
-  that argument.  See the SysRq documentation in Documentation/sysrq.txt
-  in your favorite kernel tree to see what letters are valid and what
-  they do.
+  that argument.  See the SysRq documentation in
+  Documentation/admin-guide/sysrq.rst in your favorite kernel tree to
+  see what letters are valid and what they do.
 
 
 

Thanks,
Mauro