From: keith.busch@intel.com (Keith Busch)
Subject: compile nvme 4.13 appear error
Date: Tue, 19 Sep 2017 13:33:35 -0400 [thread overview]
Message-ID: <20170919173335.GD6180@localhost.localdomain> (raw)
In-Reply-To: <CADL4p-pCuQmoEmRrwb0skct8OEJjGsTEkfhC4guV8Pgx6rWAew@mail.gmail.com>
On Tue, Sep 19, 2017@11:27:39PM +0800, Tony Yang wrote:
> Hi,
>
> I Once again downloaded the nvme 4.13 in
> http://git.infradead.org/nvme.git, and then recompile the kernel, the
> error occurred, how can I solve it, I hope to get your help, thank you
> very much?
>
> CC [M] drivers/nvme/host/core.o
> drivers/nvme/host/core.c: In function 'nvme_alloc_mpath_ns':
> drivers/nvme/host/core.c:3111:34: error: 'NVME_FAILOVER_RETRIES'
> undeclared (first use in this function)
> if (nvme_set_ns_active(nsa, ns, NVME_FAILOVER_RETRIES)) {
> ^
> drivers/nvme/host/core.c:3111:34: note: each undeclared identifier is
> reported only once for each function it appears in
> drivers/nvme/host/core.c: In function 'nvme_trigger_failover':
> drivers/nvme/host/core.c:3277:50: error: 'NVME_FAILOVER_RETRIES'
> undeclared (first use in this function)
> if (nvme_set_ns_active(standby_ns, mpath_ns, NVME_FAILOVER_RETRIES)) {
> ^
> make[3]: *** [drivers/nvme/host/core.o] Error 1
> make[2]: *** [drivers/nvme/host] Error 2
> make[1]: *** [drivers/nvme] Error 2
> make: *** [drivers] Error 2
Like I said before, those errors do not exist in an unmodified version
of the git repo you're linking to. You've out-of-tree stuff in your
source, so you or whoever set it up broke it.
next prev parent reply other threads:[~2017-09-19 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 13:02 compile nvme 4.13 appear error Tony Yang
2017-09-18 17:27 ` Keith Busch
2017-09-19 1:57 ` Tony Yang
2017-09-19 2:10 ` Keith Busch
2017-09-19 15:27 ` Tony Yang
2017-09-19 17:33 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-15 14:08 Compile " Tony Yang
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=20170919173335.GD6180@localhost.localdomain \
--to=keith.busch@intel.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