linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@mellanox.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: build failure after merge of the hmm tree
Date: Mon, 2 Sep 2019 10:51:41 +0000	[thread overview]
Message-ID: <20190902105137.GC20@mellanox.com> (raw)
In-Reply-To: <20190902205017.3eca5b70@canb.auug.org.au>

On Mon, Sep 02, 2019 at 08:50:17PM +1000, Stephen Rothwell wrote:
> Hi all,

> 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.
> 

Looks like more kconfig trouble, can you send Dan your kconfig? I'll
drop this patch again

Thanks,
Jason

  reply	other threads:[~2019-09-02 10:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 10:50 linux-next: build failure after merge of the hmm tree Stephen Rothwell
2019-09-02 10:51 ` Jason Gunthorpe [this message]
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=20190902105137.GC20@mellanox.com \
    --to=jgg@mellanox.com \
    --cc=dan.j.williams@intel.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).