All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Saeger <tom.saeger@oracle.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Tom Saeger <tom.saeger@oracle.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/8] Documentation: fix ref to sphinx/kerneldoc.py
Date: Thu, 12 Oct 2017 15:23:42 -0500	[thread overview]
Message-ID: <65cc88dbed68dbc323f3b1ca150fbb2c948344b1.1507838726.git.tom.saeger@oracle.com> (raw)
In-Reply-To: <cover.1507838726.git.tom.saeger@oracle.com>

Signed-off-by: Tom Saeger <tom.saeger@oracle.com>
---
 Documentation/doc-guide/kernel-doc.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/doc-guide/kernel-doc.rst b/Documentation/doc-guide/kernel-doc.rst
index b24854b5d6be..0268335414ce 100644
--- a/Documentation/doc-guide/kernel-doc.rst
+++ b/Documentation/doc-guide/kernel-doc.rst
@@ -65,7 +65,7 @@ Without options, the kernel-doc directive includes all documentation comments
 from the source file.
 
 The kernel-doc extension is included in the kernel source tree, at
-``Documentation/sphinx/kernel-doc.py``. Internally, it uses the
+``Documentation/sphinx/kerneldoc.py``. Internally, it uses the
 ``scripts/kernel-doc`` script to extract the documentation comments from the
 source.
 
-- 
2.14.2

  parent reply	other threads:[~2017-10-12 20:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 20:23 [PATCH 0/8] Documentation: fix invalid Documentation refs (2) Tom Saeger
2017-10-12 20:23 ` [PATCH 1/8] Documentation: fix locking rt-mutex doc refs Tom Saeger
2017-10-12 20:23 ` Tom Saeger [this message]
2017-10-12 20:23 ` [PATCH 3/8] Documentation: fix ref to workqueue content Tom Saeger
2017-10-13  8:03   ` Jani Nikula
2017-10-12 20:23 ` [PATCH 4/8] Documentation: fix ref to coccinelle content Tom Saeger
2017-10-12 20:23 ` [PATCH 5/8] Documentation: fix ref to trace stm content Tom Saeger
2017-10-12 20:24 ` [PATCH 6/8] Documentation: fix ref to power basic-pm-debugging Tom Saeger
2017-10-12 20:46   ` Rafael J. Wysocki
2017-10-12 20:24 ` [PATCH 7/8] Documentation: fix selftests related file refs Tom Saeger
2017-10-20 16:53   ` Jerry Hoemann
2017-10-22 16:23   ` [7/8] " Guenter Roeck
2017-10-12 20:24 ` [PATCH 8/8] Documentation: fix ref to gpio.txt Tom Saeger
2017-10-16 12:03   ` Linus Walleij
2017-10-19 18:59 ` [PATCH 0/8] Documentation: fix invalid Documentation refs (2) Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=65cc88dbed68dbc323f3b1ca150fbb2c948344b1.1507838726.git.tom.saeger@oracle.com \
    --to=tom.saeger@oracle.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.