summaryrefslogtreecommitdiff
path: root/drivers/media/radio
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab+huawei@kernel.org>2020-03-04 15:54:10 +0100
committerMauro Carvalho Chehab <mchehab+huawei@kernel.org>2020-04-14 10:36:18 +0200
commit577a7ad33aeff86f6c97277b12b122a0a2ad97d7 (patch)
tree1c29f9e40be3b350ed2a30e5fa199e7c6092d5a2 /drivers/media/radio
parent32e2eae23f8fd1b90d86f4d04ca9790952d9d928 (diff)
downloadlinux-next-577a7ad33aeff86f6c97277b12b122a0a2ad97d7.tar.gz
media: docs: move driver-specific info to driver-api
Those documents don't really describe the driver API. Instead, they contain development-specific information. Yet, as the main index file describes the content of it as: "how specific kernel subsystems work from the point of view of a kernel developer" It seems to be the better fit. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Diffstat (limited to 'drivers/media/radio')
-rw-r--r--drivers/media/radio/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/media/radio/Kconfig b/drivers/media/radio/Kconfig
index f4df16df19d9..d29e29645e04 100644
--- a/drivers/media/radio/Kconfig
+++ b/drivers/media/radio/Kconfig
@@ -272,7 +272,7 @@ config RADIO_RTRACK
been reported to be used by these cards.
More information is contained in the file
- <file:Documentation/media/v4l-drivers/radiotrack.rst>.
+ <file:Documentation/driver-api/media/drivers/radiotrack.rst>.
To compile this driver as a module, choose M here: the
module will be called radio-aimslab.