From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-next@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net
Cc: jason.wessel@windriver.com, akpm <akpm@linux-foundation.org>
Subject: [PATCH -next] kgdb: fix kernel-doc error
Date: Wed, 22 Oct 2008 16:34:13 -0700 [thread overview]
Message-ID: <48FFB875.2090103@xenotime.net> (raw)
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix kernel-doc format error in kgdb.h:
linux-next-20081022//include/linux/kgdb.h:308): duplicate section name 'Description'
and fix typos in that file's kernel-doc comments.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
cc: Jason Wessel <jason.wessel@windriver.com>
---
include/linux/kgdb.h | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
--- linux-next-20081022.orig/include/linux/kgdb.h
+++ linux-next-20081022/include/linux/kgdb.h
@@ -29,8 +29,7 @@ struct pt_regs;
*
* On some architectures it is required to skip a breakpoint
* exception when it occurs after a breakpoint has been removed.
- * This can be implemented in the architecture specific portion of
- * for kgdb.
+ * This can be implemented in the architecture specific portion of kgdb.
*/
extern int kgdb_skipexception(int exception, struct pt_regs *regs);
@@ -42,7 +41,7 @@ extern int kgdb_skipexception(int except
*
* This is usually needed on architectures which support SMP and
* KGDB. This function is called after all the secondary cpus have
- * been put to a know spin state and the primary CPU has control over
+ * been put to a known spin state and the primary CPU has control over
* KGDB.
*/
extern void kgdb_post_primary_code(struct pt_regs *regs, int e_vector,
@@ -65,7 +64,7 @@ struct uart_port;
/**
* kgdb_breakpoint - compiled in breakpoint
*
- * This will be impelmented a static inline per architecture. This
+ * This will be implemented as a static inline per architecture. This
* function is called by the kgdb core to execute an architecture
* specific trap to cause kgdb to enter the exception processing.
*
@@ -190,7 +189,7 @@ kgdb_arch_handle_exception(int vector, i
* @flags: Current IRQ state
*
* On SMP systems, we need to get the attention of the other CPUs
- * and get them be in a known state. This should do what is needed
+ * and get them into a known state. This should do what is needed
* to get the other CPUs to call kgdb_wait(). Note that on some arches,
* the NMI approach is not used for rounding up all the CPUs. For example,
* in case of MIPS, smp_call_function() is used to roundup CPUs. In
@@ -295,8 +294,7 @@ extern int __weak kgdb_mem2hex(char *mem
extern int __weak kgdb_hex2mem(char *buf, char *mem, int count);
/**
- * kgdb_ebin2mem - (optional arch override) Copy the binary array
- * pointed to by buf into mem.
+ * kgdb_ebin2mem - (optional arch override) Copy binary array from @buf into @mem
* @buf: source buffer
* @mem: target buffer
* @count: number of bytes in mem
reply other threads:[~2008-10-22 23: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=48FFB875.2090103@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).