summaryrefslogtreecommitdiff
path: root/Documentation/media/v4l-drivers/bttv.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/media/v4l-drivers/bttv.rst')
-rw-r--r--Documentation/media/v4l-drivers/bttv.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/media/v4l-drivers/bttv.rst b/Documentation/media/v4l-drivers/bttv.rst
index bc63b12efafd..195ccaac2816 100644
--- a/Documentation/media/v4l-drivers/bttv.rst
+++ b/Documentation/media/v4l-drivers/bttv.rst
@@ -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.