From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Christoph Hellwig <hch@lst.de>
Subject: linux-next: build failure after merge of the hmm tree
Date: Mon, 2 Sep 2019 20:50:17 +1000 [thread overview]
Message-ID: <20190902205017.3eca5b70@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3851 bytes --]
Hi all,
After merging the hmm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: "__nd_driver_register" [drivers/dax/pmem/dax_pmem_compat.ko] undefined!
ERROR: "nvdimm_namespace_common_probe" [drivers/dax/pmem/dax_pmem_core.ko] undefined!
ERROR: "devm_nsio_disable" [drivers/dax/pmem/dax_pmem_core.ko] undefined!
ERROR: "devm_nsio_enable" [drivers/dax/pmem/dax_pmem_core.ko] undefined!
ERROR: "nvdimm_setup_pfn" [drivers/dax/pmem/dax_pmem_core.ko] undefined!
ERROR: "to_nd_dax" [drivers/dax/pmem/dax_pmem_core.ko] undefined!
ERROR: "to_nd_region" [drivers/dax/pmem/dax_pmem_core.ko] undefined!
ERROR: "__nd_driver_register" [drivers/dax/pmem/dax_pmem.ko] undefined!
ERROR: "nvdimm_cmd_mask" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_blk_region_provider_data" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_blk_region_to_dimm" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_bus_attribute_group" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_fletcher64" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_attribute_group" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_blk_region_set_provider_data" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_kobj" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_pmem_region_create" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_cmd_in_size" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_region_dev" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_bus_register" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_to_bus" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_numa_attribute_group" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_in_overwrite" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_flush" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_region_acquire_lane" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_provider_data" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_volatile_region_create" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "devm_nvdimm_memremap" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_region_attribute_group" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "to_nvdimm_bus_dev" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_name" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_blk_memremap_flags" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_bus_unregister" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_cmd_dimm_desc" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_mapping_attribute_group" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_cmd_out_size" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_region_release_lane" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_device_attribute_group" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "to_nd_desc" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_has_flush" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "to_nvdimm_bus" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_bus_check_dimm_count" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "to_nd_region" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "__nvdimm_create" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "to_nvdimm" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_cmd_bus_desc" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_bus_add_badrange" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nd_region_provider_data" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "to_nd_blk_region" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_region_notify" [drivers/acpi/nfit/nfit.ko] undefined!
ERROR: "nvdimm_blk_region_create" [drivers/acpi/nfit/nfit.ko] undefined!
Caused by commit
126470c8a58b ("libnvdimm: Enable unit test infrastructure compile checks")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-09-02 10:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 10:50 Stephen Rothwell [this message]
2019-09-02 10:51 ` linux-next: build failure after merge of the hmm tree Jason Gunthorpe
2019-09-02 23:45 ` Stephen Rothwell
2019-09-03 5:31 ` Dan Williams
2019-09-03 5:42 ` Stephen Rothwell
2019-09-03 23:11 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2021-08-23 7:50 Stephen Rothwell
2021-08-23 17:33 ` Jason Gunthorpe
2021-09-01 22:01 ` Stephen Rothwell
2020-10-06 9:35 Stephen Rothwell
2020-10-06 16:41 ` Jason Gunthorpe
2020-10-12 4:19 ` Stephen Rothwell
2020-10-15 21:11 ` Stephen Rothwell
2019-11-14 5:34 Stephen Rothwell
2019-11-14 12:58 ` Jason Gunthorpe
2019-07-01 11:33 Stephen Rothwell
2019-07-01 23:10 ` Jason Gunthorpe
2019-07-03 1:28 ` Alex Deucher
2019-07-01 11:08 Stephen Rothwell
2019-07-09 0:21 ` Stephen Rothwell
2019-07-09 12:32 ` Jason Gunthorpe
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=20190902205017.3eca5b70@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).