From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: dwmw2@infradead.org
Subject: [PATCH] MTD: fix kernel-doc warnings
Date: Sun, 22 Oct 2006 19:31:50 -0700 [thread overview]
Message-ID: <20061022193150.aea33ea6.randy.dunlap@oracle.com> (raw)
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix MTD kernel-doc warnings:
Warning(/var/linsrc/linux-2619-rc2g7//include/linux/mtd/nand.h:416): No description found for parameter 'write_page'
Warning(/var/linsrc/linux-2619-rc2g7//drivers/mtd/nand/nand_base.c:1485): No description found for parameter 'raw'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/mtd/nand/nand_base.c | 1 +
include/linux/mtd/nand.h | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
--- linux-2619-rc2g7.orig/drivers/mtd/nand/nand_base.c
+++ linux-2619-rc2g7/drivers/mtd/nand/nand_base.c
@@ -1479,6 +1479,7 @@ static void nand_write_page_syndrome(str
* @buf: the data to write
* @page: page number to write
* @cached: cached programming
+ * @raw: use raw write mode
*/
static int nand_write_page(struct mtd_info *mtd, struct nand_chip *chip,
const uint8_t *buf, int page, int cached, int raw)
--- linux-2619-rc2g7.orig/include/linux/mtd/nand.h
+++ linux-2619-rc2g7/include/linux/mtd/nand.h
@@ -355,7 +355,7 @@ struct nand_buffers {
* @priv: [OPTIONAL] pointer to private chip date
* @errstat: [OPTIONAL] hardware specific function to perform additional error status checks
* (determine if errors are correctable)
- * @write_page [REPLACEABLE] High-level page write function
+ * @write_page: [REPLACEABLE] High-level page write function
*/
struct nand_chip {
---
reply other threads:[~2006-10-23 2:30 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=20061022193150.aea33ea6.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dwmw2@infradead.org \
--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
Powered by JetHome