From: kbuild test robot <lkp@intel.com>
To: Peter Pan <peterpansjtu@gmail.com>
Cc: kbuild-all@01.org, computersforpeace@gmail.com,
dwmw2@infradead.org, boris.brezillon@free-electrons.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
karlzhang@micron.com, beanhuo@micron.com,
xuejiancheng@huawei.com, Peter Pan <peterpandong@micron.com>
Subject: Re: [PATCH 03/11] mtd: nand_bbt: add new API definitions
Date: Mon, 14 Mar 2016 11:47:47 +0800 [thread overview]
Message-ID: <201603141158.lXLz6cm4%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457923684-13505-4-git-send-email-peterpandong@micron.com>
[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]
Hi Peter,
[auto build test WARNING on next-20160311]
[cannot apply to mtd/master v4.5-rc7 v4.5-rc6 v4.5-rc5 v4.5-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Peter-Pan/mtd-nand_bbt-introduce-independent-nand-BBT/20160314-105725
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
drivers/mtd/nand/nand_base.c:321: warning: Excess function parameter 'getchip' description in 'nand_block_bad'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'ops'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'info'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'options'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'bbt_td'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'bbt_md'
drivers/mtd/nand/nand_base.c:321: warning: Excess function parameter 'getchip' description in 'nand_block_bad'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'ops'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'info'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'options'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'bbt_td'
>> drivers/mtd/nand/nand_bbt.c:1409: warning: No description found for parameter 'bbt_md'
vim +/ops +1409 drivers/mtd/nand/nand_bbt.c
1393 static void nand_bbt_release(struct nand_bbt *bbt)
1394 {
1395 kfree(bbt->bbt);
1396 }
1397
1398 /**
1399 * nand_bbt_create - [NAND BBT Interface] create BBT structures for certain
1400 * MTD device
1401 * @mtd: MTD structure
1402 */
1403 struct nand_bbt *nand_bbt_create(struct mtd_info *mtd,
1404 const struct nand_bbt_ops *ops,
1405 struct nand_chip_layout_info *info,
1406 unsigned int options,
1407 struct nand_bbt_descr *bbt_td,
1408 struct nand_bbt_descr *bbt_md)
> 1409 {
1410 struct nand_bbt *bbt = kzalloc(sizeof(struct nand_bbt),
1411 GFP_KERNEL);
1412 int ret;
1413
1414 if (!bbt)
1415 return ERR_PTR(-ENOMEM);
1416
1417 bbt->mtd = mtd;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6294 bytes --]
next prev parent reply other threads:[~2016-03-14 3:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 2:47 [PATCH 00/11] mtd: nand_bbt: introduce independent nand BBT Peter Pan
2016-03-14 2:47 ` [PATCH 01/11] mtd: nand_bbt: new header for nand family BBT Peter Pan
2016-03-14 2:47 ` [PATCH 02/11] mtd: nand_bbt: introduce BBT related data structure Peter Pan
2016-03-25 8:35 ` Boris Brezillon
2016-03-28 8:09 ` Peter Pan
2016-03-29 8:16 ` Boris Brezillon
2016-04-18 6:22 ` Peter Pan
2016-04-18 7:44 ` Boris Brezillon
2016-04-19 0:40 ` Peter Pan
2016-04-19 7:34 ` Boris Brezillon
2016-05-04 1:36 ` Peter Pan
2016-05-04 20:33 ` Boris Brezillon
2016-05-17 1:03 ` Peter Pan
2016-06-17 2:38 ` Peter Pan
2016-06-21 13:27 ` Boris Brezillon
2016-03-14 2:47 ` [PATCH 03/11] mtd: nand_bbt: add new API definitions Peter Pan
2016-03-14 3:47 ` kbuild test robot [this message]
2016-03-25 8:49 ` Boris Brezillon
2016-03-28 7:56 ` Peter Pan
2016-03-14 2:47 ` [PATCH 04/11] mtd: nand_bbt: add nand_bbt_markbad_factory() interface Peter Pan
2016-03-14 2:47 ` [PATCH 05/11] mtd: nand: use new BBT API instead of old ones Peter Pan
2016-03-25 8:51 ` Boris Brezillon
2016-03-28 8:12 ` Peter Pan
2016-03-29 8:07 ` Boris Brezillon
2016-03-14 2:47 ` [PATCH 06/11] mtd: nand_bbt: use struct nand_bbt_ops in BBT Peter Pan
2016-03-14 2:48 ` [PATCH 07/11] mtd: nand: make nand_erase_nand() static Peter Pan
2016-03-14 2:48 ` [PATCH 08/11] mtd: nand_bbt: remove struct nand_chip from nand_bbt.c Peter Pan
2016-03-14 2:48 ` [PATCH 09/11] mtd: nand_bbt: remove old API definitions Peter Pan
2016-03-14 2:48 ` [PATCH 10/11] mtd: nand_bbt: remove NAND_BBT_DYNAMICSTRUCT macro Peter Pan
2016-03-14 2:48 ` [PATCH 11/11] mtd: nand: remove nand_chip.bbt Peter Pan
2016-03-14 2:57 ` [PATCH 00/11] mtd: nand_bbt: introduce independent nand BBT Peter Pan
2016-03-16 12:57 ` Boris Brezillon
2016-03-23 20:57 ` Ezequiel Garcia
2016-03-28 8:20 ` Peter Pan
2016-03-29 8:02 ` Boris Brezillon
2016-03-25 8:50 ` Boris Brezillon
2016-03-28 7:56 ` Peter Pan
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=201603141158.lXLz6cm4%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=karlzhang@micron.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=peterpandong@micron.com \
--cc=peterpansjtu@gmail.com \
--cc=xuejiancheng@huawei.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
all inboxes | Powered by JetHome®