From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: <linux-mtd@lists.infradead.org>,
Richard Weinberger <richard@nod.at>,
Archit Taneja <architt@codeaurora.org>
Subject: Re: [PATCH] mtd: nand: remove kerneldoc for removed function parameter
Date: Fri, 11 Mar 2016 10:47:28 +0100 [thread overview]
Message-ID: <20160311104728.77725c12@bbrezillon> (raw)
In-Reply-To: <1457642843-16935-1-git-send-email-computersforpeace@gmail.com>
On Thu, 10 Mar 2016 12:47:23 -0800
Brian Norris <computersforpeace@gmail.com> wrote:
> The 'getchip' parameter is gone as of commit 9f3e04297b08 ("mtd: nand:
> don't select chip in nand_chip's block_bad op"), so kill the doc with
> it.
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> drivers/mtd/nand/nand_base.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
> index d49b01df3513..b6facac54fc0 100644
> --- a/drivers/mtd/nand/nand_base.c
> +++ b/drivers/mtd/nand/nand_base.c
> @@ -313,7 +313,6 @@ static void nand_read_buf16(struct mtd_info *mtd, uint8_t *buf, int len)
> * nand_block_bad - [DEFAULT] Read bad block marker from the chip
> * @mtd: MTD device structure
> * @ofs: offset from device start
> - * @getchip: 0, if the chip is already selected
> *
> * Check, if the block is bad.
> */
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-11 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 20:47 [PATCH] mtd: nand: remove kerneldoc for removed function parameter Brian Norris
2016-03-11 9:47 ` Boris Brezillon [this message]
2016-03-11 17:41 ` Brian Norris
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=20160311104728.77725c12@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=architt@codeaurora.org \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--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 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).