From: Randy Dunlap <randy.dunlap@oracle.com>
To: kgdb-bugreport@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Cc: jason.wessel@windriver.com, akpm <akpm@linux-foundation.org>
Subject: [PATCH -mm] fix kgdb kernel-doc
Date: Sat, 28 Jul 2007 09:38:31 -0700 [thread overview]
Message-ID: <20070728093831.8dff0e15.randy.dunlap@oracle.com> (raw)
From: Randy Dunlap <randy.dunlap@oracle.com>
No kernel-doc comments in this file, although kgdb.tmpl implies that
it needs some:
Warning(linux-2.6.23-rc1-mm1//kernel/kgdb.c): no structured comments found
Add kernel-doc notation in kgdb.h for:
Warning(linux-2.6.23-rc1-mm1//include/linux/kgdb.h:225): No description found for parameter 'remove_all_hw_break'
Warning(linux-2.6.23-rc1-mm1//include/linux/kgdb.h:225): No description found for parameter 'correct_hw_break'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/DocBook/kgdb.tmpl | 4 +++-
include/linux/kgdb.h | 4 ++++
2 files changed, 7 insertions(+), 1 deletion(-)
--- linux-2.6.23-rc1-mm1.orig/Documentation/DocBook/kgdb.tmpl
+++ linux-2.6.23-rc1-mm1/Documentation/DocBook/kgdb.tmpl
@@ -235,7 +235,9 @@
and are optionally implemented. Some functions (with _hw_ in the name)
end up being required on arches which use hardware breakpoints.
</para>
-!Ikernel/kgdb.c
+<!--
+X!Ikernel/kgdb.c
+-->
</chapter>
<chapter id="DriverSpecificFunctions">
<title>Driver-Specific Functions</title>
--- linux-2.6.23-rc1-mm1.orig/include/linux/kgdb.h
+++ linux-2.6.23-rc1-mm1/include/linux/kgdb.h
@@ -207,6 +207,10 @@ extern int kgdb_arch_remove_breakpoint(u
* breakpoint.
* @remove_hw_breakpoint: Allow an architecture to specify how to remove a
* hardware breakpoint.
+ * @remove_all_hw_break: Allow an architecture to specify how to remove all
+ * hardware breakpoints.
+ * @correct_hw_break: Allow an architecture to specify how to correct the
+ * hardware debug registers.
*
* The @shadowth flag is an option to shadow information not retrievable by
* gdb otherwise. This is deprecated in favor of a binutils which supports
reply other threads:[~2007-07-28 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070728093831.8dff0e15.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.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 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®