[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190706094802.0963c374@canb.auug.org.au>
Date: Sat, 6 Jul 2019 09:48:02 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Pankaj Gupta <pagupta@...hat.com>,
Yuval Shaia <yuval.shaia@...cle.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Jakub Staron <jstaron@...gle.com>,
Cornelia Huck <cohuck@...hat.com>,
kbuild test robot <lkp@...el.com>
Subject: Re: linux-next: build failure after merge of the nvdimm tree
Hi Dan,
On Fri, 5 Jul 2019 15:32:19 -0700 Dan Williams <dan.j.williams@...el.com> wrote:
>
> On Fri, Jul 5, 2019 at 12:20 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > After merging the nvdimm tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from <command-line>:32:
> > ./usr/include/linux/virtio_pmem.h:19:2: error: unknown type name 'uint64_t'
> > uint64_t start;
> > ^~~~~~~~
> > ./usr/include/linux/virtio_pmem.h:20:2: error: unknown type name 'uint64_t'
> > uint64_t size;
> > ^~~~~~~~
>
> /me boggles at how this sat in 0day visible tree for a long while
> without this report?
These messages are produced by a new test in the kbuild tree, so you
need both it and the nvdimm tree together to get them. That will
change after the merge window, of course.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists