From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Matias Bjørling" <m@bjorling•me>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the lightnvm tree
Date: Mon, 4 Jul 2016 14:31:53 +1000 [thread overview]
Message-ID: <20160704143153.57dacf1e@canb.auug.org.au> (raw)
In-Reply-To: <20160630125635.008b33b6@canb.auug.org.au>
Hi Matias,
On Thu, 30 Jun 2016 12:56:35 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the lightnvm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "nvm_alloc_dev" [drivers/nvme/host/nvme-core.ko] undefined!
> ERROR: "nvm_alloc_dev" [drivers/block/null_blk.ko] undefined!
>
> Caused by commit
>
> 3daf1adc80a8 ("lightnvm: let drivers control the lifetime of nvm_dev")
>
> I have used the lightnvm tree from next-20160629 for today.
I am still getting this error.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-07-04 4:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 2:56 linux-next: build failure after merge of the lightnvm tree Stephen Rothwell
2016-07-04 4:31 ` Stephen Rothwell [this message]
2016-07-04 7:06 ` Matias Bjørling
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=20160704143153.57dacf1e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=m@bjorling$(echo .)me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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