From: kbuild test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@01.org, axboe@kernel.dk, keith.busch@intel.com,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jay Freyensee <james.p.freyensee@intel.com>,
Ming Lin <ming.l@ssi.samsung.com>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH 3/3] nvme-loop: add a NVMe loopback host driver
Date: Tue, 7 Jun 2016 06:00:41 +0800 [thread overview]
Message-ID: <201606070531.Qm5mRk3M%fengguang.wu@intel.com> (raw)
In-Reply-To: <1465248177-17970-4-git-send-email-hch@lst.de>
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
Hi,
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.7-rc2 next-20160606]
[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/Christoph-Hellwig/block-Export-blk_poll/20160607-052554
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from drivers/nvme/target/loop.c:22:0:
drivers/nvme/target/nvmet.h:93:34: error: field 'disc_addr' has incomplete type
struct nvmf_disc_rsp_page_entry disc_addr;
^~~~~~~~~
drivers/nvme/target/nvmet.h:134:19: error: 'NVMF_NQN_FIELD_LEN' undeclared here (not in a function)
char subsysnqn[NVMF_NQN_FIELD_LEN];
^~~~~~~~~~~~~~~~~~
drivers/nvme/target/nvmet.h:139:24: error: field 'type' has incomplete type
enum nvme_subsys_type type;
^~~~
drivers/nvme/target/nvmet.h: In function 'nvmet_data_dir':
drivers/nvme/target/nvmet.h:249:9: error: implicit declaration of function 'nvme_is_write' [-Werror=implicit-function-declaration]
return nvme_is_write(req->cmd) ? DMA_FROM_DEVICE : DMA_TO_DEVICE;
^~~~~~~~~~~~~
drivers/nvme/target/loop.c: At top level:
>> drivers/nvme/target/loop.c:24:29: fatal error: ../host/fabrics.h: No such file or directory
#include "../host/fabrics.h"
^
cc1: some warnings being treated as errors
compilation terminated.
vim +24 drivers/nvme/target/loop.c
18 #include <linux/nvme.h>
19 #include <linux/module.h>
20 #include <linux/parser.h>
21 #include <linux/t10-pi.h>
22 #include "nvmet.h"
23 #include "../host/nvme.h"
> 24 #include "../host/fabrics.h"
25
26 #define NVME_LOOP_AQ_DEPTH 256
27
---
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: 54457 bytes --]
next prev parent reply other threads:[~2016-06-06 23:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 21:22 NVMe over Fabrics target implementation Christoph Hellwig
2016-06-06 21:22 ` [PATCH 1/3] block: Export blk_poll Christoph Hellwig
2016-06-07 6:49 ` Nicholas A. Bellinger
2016-06-06 21:22 ` [PATCH 2/3] nvmet: add a generic NVMe target Christoph Hellwig
2016-06-06 21:22 ` [PATCH 3/3] nvme-loop: add a NVMe loopback host driver Christoph Hellwig
2016-06-06 22:00 ` kbuild test robot [this message]
2016-06-07 6:23 ` NVMe over Fabrics target implementation Nicholas A. Bellinger
2016-06-07 10:55 ` Christoph Hellwig
2016-06-08 5:21 ` Nicholas A. Bellinger
2016-06-08 12:19 ` Christoph Hellwig
2016-06-08 13:12 ` Sagi Grimberg
2016-06-08 13:46 ` Christoph Hellwig
2016-06-09 4:36 ` Nicholas A. Bellinger
2016-06-09 13:46 ` Christoph Hellwig
2016-06-09 3:32 ` Nicholas A. Bellinger
2016-06-07 21:02 ` Andy Grover
2016-06-07 21:10 ` Ming Lin
2016-06-07 17:01 ` Bart Van Assche
2016-06-07 17:31 ` Christoph Hellwig
2016-06-07 18:11 ` Bart Van Assche
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=201606070531.Qm5mRk3M%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=james.p.freyensee@intel.com \
--cc=kbuild-all@01.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.l@ssi.samsung.com \
--cc=sagi@grimberg.me \
/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®