All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Matias Bjørling" <m@bjorling.me>
Cc: kbuild-all@01.org, hch@infradead.org, axboe@fb.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvme@lists.infradead.org, keith.busch@intel.com,
	jg@lightnvm.io, Stephen.Bates@pmcs.com,
	"Matias Bjørling" <m@bjorling.me>
Subject: Re: [PATCH v11 5/5] nvme: LightNVM support
Date: Sat, 17 Oct 2015 01:15:36 +0800	[thread overview]
Message-ID: <201510170104.xJh18mvo%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445001655-16370-6-git-send-email-m@bjorling.me>

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

Hi Matias,

[auto build test ERROR on block/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Matias-Bj-rling/Support-for-Open-Channel-SSDs/20151016-212550
config: x86_64-rhel (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

>> drivers/nvme/host/lightnvm.c:547:6: error: conflicting types for 'nvme_nvm_unregister'
    void nvme_nvm_unregister(char *disk_name) {};
         ^
   In file included from drivers/nvme/host/lightnvm.c:23:0:
   drivers/nvme/host/nvme.h:141:6: note: previous declaration of 'nvme_nvm_unregister' was here
    void nvme_nvm_unregister(struct request_queue *q, char *disk_name);
         ^

vim +/nvme_nvm_unregister +547 drivers/nvme/host/lightnvm.c

   541	}
   542	#else
   543	int nvme_nvm_register(struct request_queue *q, char *disk_name)
   544	{
   545		return 0;
   546	}
 > 547	void nvme_nvm_unregister(char *disk_name) {};
   548	int nvme_nvm_ns_supported(struct nvme_ns *ns, struct nvme_id_ns *id)
   549	{
   550		return 0;

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

WARNING: multiple messages have this Message-ID (diff)
From: lkp@intel.com (kbuild test robot)
Subject: [PATCH v11 5/5] nvme: LightNVM support
Date: Sat, 17 Oct 2015 01:15:36 +0800	[thread overview]
Message-ID: <201510170104.xJh18mvo%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445001655-16370-6-git-send-email-m@bjorling.me>

Hi Matias,

[auto build test ERROR on block/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Matias-Bj-rling/Support-for-Open-Channel-SSDs/20151016-212550
config: x86_64-rhel (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

>> drivers/nvme/host/lightnvm.c:547:6: error: conflicting types for 'nvme_nvm_unregister'
    void nvme_nvm_unregister(char *disk_name) {};
         ^
   In file included from drivers/nvme/host/lightnvm.c:23:0:
   drivers/nvme/host/nvme.h:141:6: note: previous declaration of 'nvme_nvm_unregister' was here
    void nvme_nvm_unregister(struct request_queue *q, char *disk_name);
         ^

vim +/nvme_nvm_unregister +547 drivers/nvme/host/lightnvm.c

   541	}
   542	#else
   543	int nvme_nvm_register(struct request_queue *q, char *disk_name)
   544	{
   545		return 0;
   546	}
 > 547	void nvme_nvm_unregister(char *disk_name) {};
   548	int nvme_nvm_ns_supported(struct nvme_ns *ns, struct nvme_id_ns *id)
   549	{
   550		return 0;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/octet-stream
Size: 35276 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20151017/ecdc9ab0/attachment-0001.obj>

  reply	other threads:[~2015-10-16 17:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 13:20 [PATCH v11 0/5] Support for Open-Channel SSDs Matias Bjørling
2015-10-16 13:20 ` Matias Bjørling
2015-10-16 13:20 ` Matias Bjørling
2015-10-16 13:20 ` [PATCH v11 1/5] lightnvm: " Matias Bjørling
2015-10-16 13:20   ` Matias Bjørling
2015-10-16 13:20   ` Matias Bjørling
2015-10-16 13:20 ` [PATCH v11 2/5] gennvm: Generic NVM manager Matias Bjørling
2015-10-16 13:20   ` Matias Bjørling
2015-10-16 13:20 ` [PATCH v11 3/5] rrpc: Round-robin sector target with cost-based gc Matias Bjørling
2015-10-16 13:20   ` Matias Bjørling
2015-10-16 13:20 ` [PATCH v11 4/5] null_nvm: LightNVM test driver Matias Bjørling
2015-10-16 13:20   ` Matias Bjørling
2015-10-16 13:20   ` Matias Bjørling
2015-10-16 13:20 ` [PATCH v11 5/5] nvme: LightNVM support Matias Bjørling
2015-10-16 13:20   ` Matias Bjørling
2015-10-16 17:15   ` kbuild test robot [this message]
2015-10-16 17:15     ` kbuild test robot

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=201510170104.xJh18mvo%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Stephen.Bates@pmcs.com \
    --cc=axboe@fb.com \
    --cc=hch@infradead.org \
    --cc=jg@lightnvm.io \
    --cc=kbuild-all@01.org \
    --cc=keith.busch@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=m@bjorling.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.