linux-nvdimm.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@linux.vnet.ibm.com>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	linuxppc-dev@lists.ozlabs.org
Cc: linux-nvdimm@lists.01.org
Subject: [next-20190919] Build failure: undefined "hash__has_transparent_hugepage
Date: Fri, 20 Sep 2019 16:47:21 +0530	[thread overview]
Message-ID: <55656126-2DA5-480B-9678-6529453109B3@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190919160641.GR3642@sirena.co.uk>


> On 19-Sep-2019, at 9:36 PM, Mark Brown <broonie@kernel.org> wrote:
> 
> Hi all,
> 
> Changes since 20190918:
> 
> The btrfs-kave tree gained a conflict with Linus' tree which I wasn't
> comfortable resolving so I skipped the tre for today.
> 
> The ext4 tree gained a conflict with Linus' tree which I fixed up.
> 
> The nvdimm tree gained a conflict with the libnvdimm-fixes tree which I
> fixed up.
> 
next-20190919 fails to build on ppc64le with following error:

  WRAP    arch/powerpc/boot/zImage.pseries
  WRAP    arch/powerpc/boot/zImage.epapr
  Building modules, stage 2.
  MODPOST 1979 modules
ERROR: "hash__has_transparent_hugepage" [drivers/nvdimm/libnvdimm.ko] undefined!
ERROR: "radix__has_transparent_hugepage" [drivers/nvdimm/libnvdimm.ko] undefined!
WARNING: "fuse_put_request" [fs/fuse/fuse] is a static EXPORT_SYMBOL_GPL
make[2]: *** [__modpost] Error 1
make[1]: *** [modules] Error 2

config attached.

Thanks
-Sachin

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

           reply	other threads:[~2019-09-20 11:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190919160641.GR3642@sirena.co.uk>]

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=55656126-2DA5-480B-9678-6529453109B3@linux.vnet.ibm.com \
    --to=sachinp@linux.vnet.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).