aboutsummaryrefslogtreecommitdiff
path: root/Documentation/driver-api/media
diff options
context:
space:
mode:
authorGravatar Mauro Carvalho Chehab <mchehab+huawei@kernel.org> 2021-06-05 14:40:12 +0200
committerGravatar Mauro Carvalho Chehab <mchehab+huawei@kernel.org> 2021-06-16 07:26:46 +0200
commita169c44e58190bbdaf9c8d345cd445eec2c2b010 (patch)
tree38821b3f943ad3257ae6e8894cc003feec9c4977 /Documentation/driver-api/media
parentmedia: userspace-api: avoid using ReST :doc:`foo` markup (diff)
downloadlinux-a169c44e58190bbdaf9c8d345cd445eec2c2b010.tar.gz
linux-a169c44e58190bbdaf9c8d345cd445eec2c2b010.tar.bz2
linux-a169c44e58190bbdaf9c8d345cd445eec2c2b010.zip
media: driver-api: drivers: avoid using ReST :doc:`foo` markup
The :doc:`foo` tag is auto-generated via automarkup.py. So, use the filename at the sources, instead of :doc:`foo`. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Diffstat (limited to 'Documentation/driver-api/media')
-rw-r--r--Documentation/driver-api/media/drivers/bttv-devel.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/driver-api/media/drivers/bttv-devel.rst b/Documentation/driver-api/media/drivers/bttv-devel.rst
index c9aa8b95a5e5..0885a04563a9 100644
--- a/Documentation/driver-api/media/drivers/bttv-devel.rst
+++ b/Documentation/driver-api/media/drivers/bttv-devel.rst
@@ -21,7 +21,7 @@ log, telling which card type is used. Like this one::
You should verify this is correct. If it isn't, you have to pass the
correct board type as insmod argument, ``insmod bttv card=2`` for
-example. The file :doc:`/admin-guide/media/bttv-cardlist` has a list
+example. The file Documentation/admin-guide/media/bttv-cardlist.rst has a list
of valid arguments for card.
If your card isn't listed there, you might check the source code for