summaryrefslogtreecommitdiff
path: root/Documentation/media/v4l-drivers/bttv.rst
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2016-12-13 10:36:39 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2016-12-13 10:36:39 +0100
commitc24889167583c2e7fbd1a9e12ef508c8405f6fd4 (patch)
tree4be6b8654d135b554253b6ab22c314260a413751 /Documentation/media/v4l-drivers/bttv.rst
parent38bf57fa7b671f2bf7530888aa8199450265c5c8 (diff)
parent868c97a846a73e937d835b09b8c885a69df50ec8 (diff)
downloadlinux-next-c24889167583c2e7fbd1a9e12ef508c8405f6fd4.tar.gz
Merge tag 'docs-4.10' of git://git.lwn.net/linux into drm-misc-next
Backmerge the docs-next branch from Jon into drm-misc so that we can apply the dma-buf documentation cleanup patches. Git found a conflict where there was none because both drm-misc and docs had identical patches to clean up file rename issues in the rst include directives. Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Diffstat (limited to 'Documentation/media/v4l-drivers/bttv.rst')
-rw-r--r--Documentation/media/v4l-drivers/bttv.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/media/v4l-drivers/bttv.rst b/Documentation/media/v4l-drivers/bttv.rst
index 7abc1c9a261b..bc63b12efafd 100644
--- a/Documentation/media/v4l-drivers/bttv.rst
+++ b/Documentation/media/v4l-drivers/bttv.rst
@@ -304,10 +304,10 @@ bug. It is very helpful if you can tell where exactly it broke
With a hard freeze you probably doesn't find anything in the logfiles.
The only way to capture any kernel messages is to hook up a serial
console and let some terminal application log the messages. /me uses
-screen. See Documentation/serial-console.txt for details on setting
+screen. See Documentation/admin-guide/serial-console.rst for details on setting
up a serial console.
-Read Documentation/oops-tracing.txt to learn how to get any useful
+Read Documentation/admin-guide/oops-tracing.rst to learn how to get any useful
information out of a register+stack dump printed by the kernel on
protection faults (so-called "kernel oops").