From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [PATCH] mtd: nand: Fix nanddev_pos_next_page() kernel-doc header
Date: Tue, 6 Nov 2018 17:37:13 +0100 [thread overview]
Message-ID: <20181106173713.38806c5e@bbrezillon> (raw)
In-Reply-To: <20181106172946.10f9c3ca@xps13>
On Tue, 6 Nov 2018 17:29:46 +0100
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Boris Brezillon <boris.brezillon@bootlin.com> wrote on Tue, 6 Nov 2018
> 17:25:37 +0100:
>
> > Function name is wrong in the kernel-doc header.
> >
Oops, forgot to add
Fixes: 9c3736a3de21 ("mtd: nand: Add core infrastructure to deal with NAND devices")
> > Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> > ---
> > include/linux/mtd/nand.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
> > index 7ff3770e468b..12d75402472a 100644
> > --- a/include/linux/mtd/nand.h
> > +++ b/include/linux/mtd/nand.h
> > @@ -583,7 +583,7 @@ static inline void nanddev_pos_next_eraseblock(struct nand_device *nand,
> > }
> >
> > /**
> > - * nanddev_pos_next_eraseblock() - Move a position to the next page
> > + * nanddev_pos_next_page() - Move a position to the next page
> > * @nand: NAND device
> > * @pos: the position to update
> > *
>
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
>
> Thanks,
> Miquèl
next prev parent reply other threads:[~2018-11-06 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 16:25 [PATCH] mtd: nand: Fix nanddev_pos_next_page() kernel-doc header Boris Brezillon
2018-11-06 16:29 ` Miquel Raynal
2018-11-06 16:37 ` Boris Brezillon [this message]
2018-11-06 16:43 ` 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=20181106173713.38806c5e@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.