linux-kernel - linux-next: build failure after merge of the nvdimm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 5 Jul 2019 17:20:25 +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>
Subject: linux-next: build failure after merge of the nvdimm tree

Hi all,

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;
  ^~~~~~~~

Caused by commit

  403b7f973855 ("virtio-pmem: Add virtio pmem driver")

I have used the nvdimm tree from next-20190704 for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped