[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9c3185a576665a5d85271b6778cb6ab340ae2d6f.1507838726.git.tom.saeger@oracle.com>
Date: Thu, 12 Oct 2017 15:23:53 -0500
From: Tom Saeger <tom.saeger@...cle.com>
To: Jonathan Corbet <corbet@....net>
Cc: Tom Saeger <tom.saeger@...cle.com>,
Jani Nikula <jani.nikula@...el.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 4/8] Documentation: fix ref to coccinelle content
Signed-off-by: Tom Saeger <tom.saeger@...cle.com>
---
Documentation/process/4.Coding.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/4.Coding.rst b/Documentation/process/4.Coding.rst
index 6df19943dd4d..26b106071364 100644
--- a/Documentation/process/4.Coding.rst
+++ b/Documentation/process/4.Coding.rst
@@ -307,7 +307,7 @@ variety of potential coding problems; it can also propose fixes for those
problems. Quite a few "semantic patches" for the kernel have been packaged
under the scripts/coccinelle directory; running "make coccicheck" will run
through those semantic patches and report on any problems found. See
-Documentation/coccinelle.txt for more information.
+Documentation/dev-tools/coccinelle.rst for more information.
Other kinds of portability errors are best found by compiling your code for
other architectures. If you do not happen to have an S/390 system or a
--
2.14.2
Powered by blists - more mailing lists