From: keith.busch@intel.com (Keith Busch)
Subject: compile nvme 4.13 appear error
Date: Mon, 18 Sep 2017 22:10:19 -0400 [thread overview]
Message-ID: <20170919021019.GA5096@localhost.localdomain> (raw)
In-Reply-To: <CADL4p-pPFxsi1B0gTKutUEAdiWpHCk99NR0E4ed6Y5_eYe=p0Q@mail.gmail.com>
On Tue, Sep 19, 2017@09:57:08AM +0800, Tony Yang wrote:
> Hi, I from http://git.infradead.org/nvme.git to get 4.13 version
>
> I want to compile with nvme new kernel, So I use 4.13 version to compile.
I have the same one, and "nvme_alloc_mpath_ns" that you're producing an
error on doesn't exist in that tree. You've done something to your tree
to break it.
> I would like to ask, how can I compile a new kernel for a successful
> nvme? Thanks
Try using it as-is.
> 2017-09-19 1:27 GMT+08:00 Keith Busch <keith.busch at intel.com>:
> > On Mon, Sep 18, 2017@09:02:15PM +0800, Tony Yang wrote:
> >> Dear All
> >>
> >> I at redhat 6.5 ,kernel is 2.6.32-431.el6.x86_64?I comile nvme 4.13
> >> appear this error:
> >>
> >> [root at cescel03 nvme-nvme-4.13]# make
> >> CHK include/config/kernel.release
> >> CHK include/generated/uapi/linux/version.h
> >> CHK include/generated/utsrelease.h
> >> CHK include/generated/bounds.h
> >> CHK include/generated/timeconst.h
> >> CHK include/generated/asm-offsets.h
> >> CALL scripts/checksyscalls.sh
> >> CHK scripts/mod/devicetable-offsets.h
> >> CHK include/generated/compile.h
> >> AR drivers/nvme/host/built-in.o
> >> CC [M] drivers/nvme/host/core.o
> >> drivers/nvme/host/core.c: In function ?nvme_alloc_mpath_ns?:
> >> drivers/nvme/host/core.c:3111: error: ?NVME_FAILOVER_RETRIES?
> >> undeclared (first use in this function)
> >> drivers/nvme/host/core.c:3111: error: (Each undeclared identifier is
> >> reported only once
> >> drivers/nvme/host/core.c:3111: error: for each function it appears in.)
> >> drivers/nvme/host/core.c: In function ?nvme_trigger_failover?:
> >> drivers/nvme/host/core.c:3277: error: ?NVME_FAILOVER_RETRIES?
> >> undeclared (first use in this function)
> >> 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
> >
> > Not sure where you got this source. The 4.13 kernel doesn't contain an
> > nvme driver with such errors, so it looks like whoever packaged up your
> > source really botched it up from applying out-of-tree stuff.
next prev parent reply other threads:[~2017-09-19 2:10 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 [this message]
2017-09-19 15:27 ` Tony Yang
2017-09-19 17:33 ` Keith Busch
-- 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=20170919021019.GA5096@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