From: kbuild test robot <lkp@intel.com>
To: Kyle Roeschley <kyle.roeschley@ni.com>
Cc: kbuild-all@01.org, boris.brezillon@free-electrons.com,
richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com,
beanhuo@micron.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, nathan.sullivan@ni.com,
xander.huff@ni.com, peterpansjtu@gmail.com
Subject: Re: [PATCH v6 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails
Date: Sat, 13 Aug 2016 03:30:15 +0800 [thread overview]
Message-ID: <201608130359.gLedtnLc%fengguang.wu@intel.com> (raw)
In-Reply-To: <1471024490-32348-2-git-send-email-kyle.roeschley@ni.com>
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
Hi Kyle,
[auto build test WARNING on mtd/master]
[also build test WARNING on v4.8-rc1 next-20160812]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Kyle-Roeschley/mtd-nand_bbt-Move-BBT-block-selection-logic-out-of-write_bbt/20160813-015713
base: git://git.infradead.org/linux-mtd.git master
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
>> drivers/mtd/nand/nand_bbt.c:685: warning: No description found for parameter 'block'
>> drivers/mtd/nand/nand_bbt.c:685: warning: Excess function parameter 'md' description in 'mark_bbt_block_bad'
drivers/mtd/nand/nand_bbt.c:1: warning: no structured comments found
>> drivers/mtd/nand/nand_bbt.c:685: warning: No description found for parameter 'block'
>> drivers/mtd/nand/nand_bbt.c:685: warning: Excess function parameter 'md' description in 'mark_bbt_block_bad'
vim +/block +685 drivers/mtd/nand/nand_bbt.c
669
670 /**
671 * mark_bbt_block_bad - Mark one of the block reserved for BBT bad
672 * @this: the NAND device
673 * @td: the BBT description
674 * @md: the mirror BBT descriptor
675 * @chip: the CHIP selector
676 *
677 * Blocks reserved for BBT can become bad. This functions is an helper to mark
678 * such blocks as bad. It takes care of updating the in-memory BBT, marking the
679 * block as bad using a bad block marker and invalidating the associated
680 * td->pages[] entry.
681 */
682 static void mark_bbt_block_bad(struct nand_chip *this,
683 struct nand_bbt_descr *td,
684 int chip, int block)
> 685 {
686 struct mtd_info *mtd = nand_to_mtd(this);
687 loff_t to;
688 int res;
689
690 bbt_mark_entry(this, block, BBT_BLOCK_WORN);
691
692 to = (loff_t)block << this->bbt_erase_shift;
693 res = this->block_markbad(mtd, to);
---
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: 6366 bytes --]
next prev parent reply other threads:[~2016-08-12 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 17:54 [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt() Kyle Roeschley
2016-08-12 17:54 ` [PATCH v6 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails Kyle Roeschley
2016-08-12 19:30 ` kbuild test robot [this message]
2016-08-12 19:15 ` [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt() Boris Brezillon
2016-08-12 19:47 ` Kyle Roeschley
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=201608130359.gLedtnLc%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=kbuild-all@01.org \
--cc=kyle.roeschley@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nathan.sullivan@ni.com \
--cc=peterpansjtu@gmail.com \
--cc=richard@nod.at \
--cc=xander.huff@ni.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®