From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Jason Wessel <jason.wessel@windriver.com>,
Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 09/13] lib: update location of kgdb documentation
Date: Sun, 14 May 2017 12:38:43 -0300 [thread overview]
Message-ID: <e5e6b87b9cfc8a5b92073f18f7a40eef70569186.1494775891.git.mchehab@s-opensource.com> (raw)
In-Reply-To: <cover.1494775891.git.mchehab@s-opensource.com>
In-Reply-To: <cover.1494775891.git.mchehab@s-opensource.com>
The documentation was moved from DocBook directory.
Update its location.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
---
lib/Kconfig.kgdb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Kconfig.kgdb b/lib/Kconfig.kgdb
index 533f912638ed..ab4ff0eea776 100644
--- a/lib/Kconfig.kgdb
+++ b/lib/Kconfig.kgdb
@@ -13,7 +13,7 @@ menuconfig KGDB
CONFIG_FRAME_POINTER to aid in producing more reliable stack
backtraces in the external debugger. Documentation of
kernel debugger is available at http://kgdb.sourceforge.net
- as well as in DocBook form in Documentation/DocBook/. If
+ as well as in Documentation/dev-tools/kgdb.rst. If
unsure, say N.
if KGDB
--
2.9.3
next prev parent reply other threads:[~2017-05-14 15:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1494775891.git.mchehab@s-opensource.com>
2017-05-14 15:38 ` [PATCH 01/13] docs-rst: convert lsm from DocBook to ReST Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 02/13] docs: remove DocBook from the building system Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 03/13] docs: update old references for DocBook from the documentation Mauro Carvalho Chehab
2017-05-15 2:07 ` SeongJae Park
2017-05-14 15:38 ` [PATCH 04/13] MAINTAINERS: update old references for DocBook directory Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 05/13] ata: update references for libata documentation Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 06/13] ia64, scsi: update references for the device-io book Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 07/13] irq: update genericirq book location Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 08/13] fs: update location of filesystems documentation Mauro Carvalho Chehab
2017-05-14 15:38 ` Mauro Carvalho Chehab [this message]
2017-05-14 15:38 ` [PATCH 10/13] sound: fix the comments that refers to kernel-doc Mauro Carvalho Chehab
2017-05-15 9:04 ` Takashi Iwai
2017-05-16 10:46 ` Mauro Carvalho Chehab
2017-05-16 10:50 ` Takashi Iwai
2017-05-16 10:55 ` Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 11/13] fs: fix the location of the kernel-api book Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 12/13] usb: fix the comment with regards to DocBook Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 13/13] docs-rst: get rid of Documentation/sphinx/tmplcvt script Mauro Carvalho Chehab
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=e5e6b87b9cfc8a5b92073f18f7a40eef70569186.1494775891.git.mchehab@s-opensource.com \
--to=mchehab@s-opensource.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jason.wessel@windriver.com \
--cc=jslaby@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®