aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristophe JAILLET <christophe.jaillet@wanadoo.fr>2017-10-20 15:49:14 -0400
committerJonathan Corbet <corbet@lwn.net>2017-10-31 04:03:58 -0400
commited6e26baa7431ebfad890f275e191e32b5a4103c (patch)
treef2b41073378c9d50496642ab1b9b9ceb1a722fbc
parent45653c845b0c670b7a194acc6a90bc70aa049252 (diff)
bug-hunting.rst: Fix an example and a typo in a Sphinx tag
- Use the same file name in the explanation and in the example (conex.c vs sonixj.c) - Add a missing ':' in a :ref: tag which leads to incorrect Shpinx output - Add some missing ',' and ';' Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/admin-guide/bug-hunting.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/admin-guide/bug-hunting.rst b/Documentation/admin-guide/bug-hunting.rst
index 08c4b1308189..f278b289e260 100644
--- a/Documentation/admin-guide/bug-hunting.rst
+++ b/Documentation/admin-guide/bug-hunting.rst
@@ -240,7 +240,7 @@ In order to report it upstream, you should identify the mailing list
240used for the development of the affected code. This can be done by using 240used for the development of the affected code. This can be done by using
241the ``get_maintainer.pl`` script. 241the ``get_maintainer.pl`` script.
242 242
243For example, if you find a bug at the gspca's conex.c file, you can get 243For example, if you find a bug at the gspca's sonixj.c file, you can get
244their maintainers with:: 244their maintainers with::
245 245
246 $ ./scripts/get_maintainer.pl -f drivers/media/usb/gspca/sonixj.c 246 $ ./scripts/get_maintainer.pl -f drivers/media/usb/gspca/sonixj.c
@@ -257,7 +257,7 @@ Please notice that it will point to:
257 Tejun and Bhaktipriya (in this specific case, none really envolved on the 257 Tejun and Bhaktipriya (in this specific case, none really envolved on the
258 development of this file); 258 development of this file);
259- The driver maintainer (Hans Verkuil); 259- The driver maintainer (Hans Verkuil);
260- The subsystem maintainer (Mauro Carvalho Chehab) 260- The subsystem maintainer (Mauro Carvalho Chehab);
261- The driver and/or subsystem mailing list (linux-media@vger.kernel.org); 261- The driver and/or subsystem mailing list (linux-media@vger.kernel.org);
262- the Linux Kernel mailing list (linux-kernel@vger.kernel.org). 262- the Linux Kernel mailing list (linux-kernel@vger.kernel.org).
263 263
@@ -274,14 +274,14 @@ Fixing the bug
274-------------- 274--------------
275 275
276If you know programming, you could help us by not only reporting the bug, 276If you know programming, you could help us by not only reporting the bug,
277but also providing us with a solution. After all open source is about 277but also providing us with a solution. After all, open source is about
278sharing what you do and don't you want to be recognised for your genius? 278sharing what you do and don't you want to be recognised for your genius?
279 279
280If you decide to take this way, once you have worked out a fix please submit 280If you decide to take this way, once you have worked out a fix please submit
281it upstream. 281it upstream.
282 282
283Please do read 283Please do read
284ref:`Documentation/process/submitting-patches.rst <submittingpatches>` though 284:ref:`Documentation/process/submitting-patches.rst <submittingpatches>` though
285to help your code get accepted. 285to help your code get accepted.
286 286
287 287