From: Xiaolei Li <xiaolei.li@mediatek.com>
To: <boris.brezillon@bootlin.com>, <richard@nod.at>
Cc: <linux-mtd@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<srv_heupstream@mediatek.com>, <xiaolei.li@mediatek.com>
Subject: [PATCH v2 2/2] mtd: nand: Fix some function description mismatches in core.c
Date: Thu, 29 Mar 2018 09:34:59 +0800 [thread overview]
Message-ID: <1522287299-12620-3-git-send-email-xiaolei.li@mediatek.com> (raw)
In-Reply-To: <1522287299-12620-1-git-send-email-xiaolei.li@mediatek.com>
In core.c, some function descriptions do not match function
definitions. Just fix these mismatches.
Signed-off-by: Xiaolei Li <xiaolei.li@mediatek.com>
---
drivers/mtd/nand/core.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/mtd/nand/core.c b/drivers/mtd/nand/core.c
index f237a68..d0cd6f8 100644
--- a/drivers/mtd/nand/core.c
+++ b/drivers/mtd/nand/core.c
@@ -51,7 +51,7 @@ bool nanddev_isbad(struct nand_device *nand, const struct nand_pos *pos)
/**
* nanddev_markbad() - Mark a block as bad
* @nand: NAND device
- * @block: block to mark bad
+ * @pos: position of the block to mark bad
*
* Mark a block bad. This function is updating the BBT if available and
* calls the low-level markbad hook (nand->ops->markbad()).
@@ -117,9 +117,9 @@ bool nanddev_isreserved(struct nand_device *nand, const struct nand_pos *pos)
/**
* nanddev_erase() - Erase a NAND portion
* @nand: NAND device
- * @block: eraseblock to erase
+ * @pos: position of the block to erase
*
- * Erases @block if it's not bad.
+ * Erases the block if it's not bad.
*
* Return: 0 in case of success, a negative error code otherwise.
*/
@@ -179,11 +179,11 @@ int nanddev_mtd_erase(struct mtd_info *mtd, struct erase_info *einfo)
/**
* nanddev_init() - Initialize a NAND device
* @nand: NAND device
- * @memorg: NAND memory organization descriptor
* @ops: NAND device operations
+ * @owner: NAND device owner
*
- * Initializes a NAND device object. Consistency checks are done on @memorg and
- * @ops. Also takes care of initializing the BBT.
+ * Initializes a NAND device object. Consistency checks are done on @ops and
+ * @nand->memorg. Also takes care of initializing the BBT.
*
* Return: 0 in case of success, a negative error code otherwise.
*/
--
1.9.1
next prev parent reply other threads:[~2018-03-29 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 1:34 [PATCH v2 0/2] Fix some function description mismatches Xiaolei Li
2018-03-29 1:34 ` [PATCH v2 1/2] mtd: Fix some function description mismatches in mtdcore.c Xiaolei Li
2018-03-29 20:24 ` Boris Brezillon
2018-03-29 1:34 ` Xiaolei Li [this message]
2018-03-29 17:54 ` [PATCH v2 2/2] mtd: nand: Fix some function description mismatches in core.c Boris Brezillon
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=1522287299-12620-3-git-send-email-xiaolei.li@mediatek.com \
--to=xiaolei.li@mediatek.com \
--cc=boris.brezillon@bootlin.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=srv_heupstream@mediatek.com \
/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