From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Xiaolei Li <xiaolei.li@mediatek.com>
Cc: <richard@nod.at>, <linux-mtd@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<srv_heupstream@mediatek.com>
Subject: Re: [PATCH 2/2] mtd: nand: Fix some function description mismatches in core.c
Date: Wed, 28 Mar 2018 13:37:50 +0200 [thread overview]
Message-ID: <20180328133750.1c42044d@bbrezillon> (raw)
In-Reply-To: <1522228438-64034-3-git-send-email-xiaolei.li@mediatek.com>
On Wed, 28 Mar 2018 17:13:58 +0800
Xiaolei Li <xiaolei.li@mediatek.com> wrote:
> 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..9f6febd 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: MTD module 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 memory organization. Also takes care of initializing the BBT.
Don't remember the exact format, but I thing you can use something
@nand->memorg
Anyway, thanks for reporting and fixing those problems in the doc.
> *
> * Return: 0 in case of success, a negative error code otherwise.
> */
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-28 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 9:13 [PATCH 0/2] Fix some function description mismatches Xiaolei Li
2018-03-28 9:13 ` [PATCH 1/2] mtd: Fix some function description mismatches in mtdcore.c Xiaolei Li
2018-03-28 9:13 ` [PATCH 2/2] mtd: nand: Fix some function description mismatches in core.c Xiaolei Li
2018-03-28 11:37 ` Boris Brezillon [this message]
2018-03-29 1:04 ` xiaolei li
2018-03-28 12:06 ` [PATCH 0/2] Fix some function description mismatches Richard Weinberger
2018-03-29 1:07 ` xiaolei li
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=20180328133750.1c42044d@bbrezillon \
--to=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 \
--cc=xiaolei.li@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