mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: kbuild-all@01.org, Christoph Hellwig <hch@infradead.org>,
	Sagi Grimberg <sagi@grimberg.me>,
	Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>,
	Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
	Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
	Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH] nvme: make nvmf_register_transport require a create_ctrl callback
Date: Fri, 27 Jan 2017 01:45:49 +0800	[thread overview]
Message-ID: <201701270119.Vec32uLQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170126152228.15330-1-jthumshirn@suse.de>

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

Hi Johannes,

[auto build test ERROR on block/for-next]
[also build test ERROR on v4.10-rc5 next-20170125]
[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/Johannes-Thumshirn/nvme-make-nvmf_register_transport-require-a-create_ctrl-callback/20170126-234702
base:   https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 6.2.0
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=ia64 

All error/warnings (new ones prefixed by >>):


vim +2066 drivers/nvme/host/rdma.c

  2060		ret = ib_register_client(&nvme_rdma_ib_client);
  2061		if (ret) {
  2062			destroy_workqueue(nvme_rdma_wq);
  2063			return ret;
  2064		}
  2065	
> 2066		return = nvmf_register_transport(&nvme_rdma_transport);
> 2067	}
  2068	
  2069	static void __exit nvme_rdma_cleanup_module(void)
  2070	{

---
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: 45519 bytes --]

      parent reply	other threads:[~2017-01-26 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 15:22 Johannes Thumshirn
2017-01-26 16:30 ` Sagi Grimberg
2017-01-27  8:00   ` Johannes Thumshirn
2017-01-26 17:45 ` kbuild test robot [this message]

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=201701270119.Vec32uLQ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=axboe@fb.com \
    --cc=hch@infradead.org \
    --cc=jthumshirn@suse.de \
    --cc=kbuild-all@01.org \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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®