From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Bolle <lkml@xs4all.nl>
Cc: Jens Axboe <axboe@fb.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Add "lightnvm: ensure that nvm_dev_ops can be used without CONFIG_NVM" to v4.4.y stable tree?
Date: Fri, 14 Oct 2016 15:47:48 +0200 [thread overview]
Message-ID: <20161014134748.GA28581@kroah.com> (raw)
In-Reply-To: <1476451721.11366.15.camel@xs4all.nl>
On Fri, Oct 14, 2016 at 03:28:41PM +0200, Paul Bolle wrote:
> Hi,
>
> I had a build of v4.4.24, with CONFIG_NVM not set, fail like this:
> drivers/block/null_blk.c:569:27: error: storage size of 'null_lnvm_dev_ops' isn't known
> static struct nvm_dev_ops null_lnvm_dev_ops;
> ^~~~~~~~~~~~~~~~~
> scripts/Makefile.build:264: recipe for target 'drivers/block/null_blk.o' failed
> make[2]: *** [drivers/block/null_blk.o] Error 1
> scripts/Makefile.build:403: recipe for target 'drivers/block' failed
> make[1]: *** [drivers/block] Error 2
> Makefile:959: recipe for target 'drivers' failed
> make: *** [drivers] Error 2
>
> Jens' commit a7fd9a4f3e81 ("lightnvm: ensure that nvm_dev_ops can be
> used without CONFIG_NVM") fixed that for me (it did require a small
> context change to get it applied to v4.4.24). Does it make sense to add
> that commit to the v4.4.y stable tree?
Makes sense to me, can you forward on a patch that applies cleanly and
I'll queue it up for the next round (after this one.)
thanks,
greg k-h
next prev parent reply other threads:[~2016-10-14 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 13:28 Add "lightnvm: ensure that nvm_dev_ops can be used without CONFIG_NVM" to v4.4.y stable tree? Paul Bolle
2016-10-14 13:47 ` Greg KH [this message]
2016-10-14 16:30 ` Paul Bolle
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=20161014134748.GA28581@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@xs4all.nl \
--cc=stable@vger.kernel.org \
/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