Linux Device Mapper development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>,
	linux-block@vger.kernel.org, dm-devel@redhat.com,
	kbuild-all@01.org, Christoph Hellwig <hch@lst.de>,
	Matias Bjorling <matias.bjorling@wdc.com>
Subject: Re: [PATCH 10/11] block: add a report_zones method
Date: Wed, 10 Oct 2018 22:40:38 +0800	[thread overview]
Message-ID: <201810102231.02JF55CT%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181010015239.24930-11-damien.lemoal@wdc.com>

[-- Attachment #1: Type: text/plain, Size: 2362 bytes --]

Hi Christoph,

I love your patch! Yet something to improve:

[auto build test ERROR on block/for-next]
[also build test ERROR on v4.19-rc7]
[cannot apply to next-20181010]
[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/Damien-Le-Moal/Zoned-block-device-support-improvements/20181010-190504
base:   https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: x86_64-randconfig-x000-201840 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers//md/dm-linear.c: In function 'linear_report_zones':
>> drivers//md/dm-linear.c:146:8: error: implicit declaration of function 'blkdev_report_zones'; did you mean 'linear_report_zones'? [-Werror=implicit-function-declaration]
     ret = blkdev_report_zones(lc->dev->bdev, linear_map_sector(ti, sector),
           ^~~~~~~~~~~~~~~~~~~
           linear_report_zones
   cc1: some warnings being treated as errors
--
   drivers//md/dm-flakey.c: In function 'flakey_report_zones':
>> drivers//md/dm-flakey.c:459:8: error: implicit declaration of function 'blkdev_report_zones'; did you mean 'flakey_report_zones'? [-Werror=implicit-function-declaration]
     ret = blkdev_report_zones(fc->dev->bdev, flakey_map_sector(ti, sector),
           ^~~~~~~~~~~~~~~~~~~
           flakey_report_zones
   cc1: some warnings being treated as errors

vim +146 drivers//md/dm-linear.c

   137	
   138	static int linear_report_zones(struct dm_target *ti, sector_t sector,
   139				       struct blk_zone *zones, unsigned int *nr_zones,
   140				       gfp_t gfp_mask)
   141	{
   142		struct linear_c *lc = (struct linear_c *) ti->private;
   143		int ret;
   144	
   145		/* Do report and remap it */
 > 146		ret = blkdev_report_zones(lc->dev->bdev, linear_map_sector(ti, sector),
   147					  zones, nr_zones, gfp_mask);
   148		if (ret != 0)
   149			return ret;
   150	
   151		if (*nr_zones)
   152			dm_remap_zone_report(ti, lc->start, zones, nr_zones);
   153		return 0;
   154	}
   155	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29768 bytes --]

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2018-10-10 14:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10  1:52 [PATCH 00/11] Zoned block device support improvements Damien Le Moal
2018-10-10  1:52 ` [PATCH 01/11] scsi: sd_zbc: Rearrange code Damien Le Moal
2018-10-10 13:25   ` Christoph Hellwig
2018-10-10  1:52 ` [PATCH 02/11] scsi: sd_zbc: Reduce boot device scan and revalidate time Damien Le Moal
2018-10-10 13:26   ` Christoph Hellwig
2018-10-10  1:52 ` [PATCH 03/11] scsi: sd_zbc: Fix sd_zbc_check_zones() error checks Damien Le Moal
2018-10-10 13:26   ` Christoph Hellwig
2018-10-10  1:52 ` [PATCH 04/11] block: Introduce blkdev_nr_zones() helper Damien Le Moal
2018-10-10 13:26   ` Christoph Hellwig
2018-10-10  1:52 ` [PATCH 05/11] block: Limit allocation of zone descriptors for report zones Damien Le Moal
2018-10-10 13:27   ` Christoph Hellwig
2018-10-10  1:52 ` [PATCH 06/11] block: Introduce BLKGETZONESZ ioctl Damien Le Moal
2018-10-10 13:27   ` Christoph Hellwig
2018-10-10 16:53   ` Bart Van Assche
2018-10-10  1:52 ` [PATCH 07/11] block: Introduce BLKGETNRZONES ioctl Damien Le Moal
2018-10-10 13:27   ` Christoph Hellwig
2018-10-10  1:52 ` [PATCH 08/11] block: Improve zone reset execution Damien Le Moal
2018-10-10 13:28   ` Christoph Hellwig
2018-10-10  1:52 ` [PATCH 09/11] block: Expose queue nr_zones in sysfs Damien Le Moal
2018-10-10 13:28   ` Christoph Hellwig
2018-10-10 14:05   ` kbuild test robot
2018-10-10 18:44   ` kbuild test robot
2018-10-10  1:52 ` [PATCH 10/11] block: add a report_zones method Damien Le Moal
2018-10-10 14:15   ` Mike Snitzer
2018-10-10 16:15     ` Mike Snitzer
2018-10-10 14:40   ` kbuild test robot [this message]
2018-10-10 15:34   ` Mike Snitzer
2018-10-10 16:25   ` kbuild test robot
2018-10-10  1:52 ` [PATCH 11/11] block: Introduce revalidate_disk_zones() Damien Le Moal
2018-10-10 13:34   ` Christoph Hellwig

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=201810102231.02JF55CT%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@wdc.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@lst.de \
    --cc=kbuild-all@01.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=matias.bjorling@wdc.com \
    --cc=snitzer@redhat.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