Re: [PATCH v1 02/11] virtio-mem: Paravirtualized memory hotplug

From: kbuild test robot <lkp@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	Michal Hocko <mhocko@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Oscar Salvador <osalvador@suse.de>,
	Igor Mammedov <imammedo@redhat.com>,
	Dave Young <dyoung@redhat.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v1 02/11] virtio-mem: Paravirtualized memory hotplug
Date: Tue, 3 Mar 2020 10:24:23 +0800	[thread overview]
Message-ID: <202003031039.To18mcrC%lkp@intel.com> (raw)
In-Reply-To: <20200302134941.315212-3-david@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]

Hi David,

I love your patch! Yet something to improve:

[auto build test ERROR on pm/linux-next]
[also build test ERROR on linus/master v5.6-rc4 next-20200302]
[cannot apply to linux/master mmotm/master]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/David-Hildenbrand/virtio-mem-paravirtualized-memory/20200303-020852
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: x86_64-randconfig-s1-20200303 (attached as .config)
compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from <command-line>:1:0:
>> ./usr/include/linux/virtio_mem.h:185:2: error: unknown type name 'uint32_t'
     uint32_t block_size;
     ^
>> ./usr/include/linux/virtio_mem.h:187:2: error: unknown type name 'uint16_t'
     uint16_t node_id;
     ^
   ./usr/include/linux/virtio_mem.h:188:2: error: unknown type name 'uint16_t'
     uint16_t padding;
     ^
>> ./usr/include/linux/virtio_mem.h:190:2: error: unknown type name 'uint64_t'
     uint64_t addr;
     ^
   ./usr/include/linux/virtio_mem.h:192:2: error: unknown type name 'uint64_t'
     uint64_t region_size;
     ^
   ./usr/include/linux/virtio_mem.h:198:2: error: unknown type name 'uint64_t'
     uint64_t usable_region_size;
     ^
   ./usr/include/linux/virtio_mem.h:203:2: error: unknown type name 'uint64_t'
     uint64_t plugged_size;
     ^
   ./usr/include/linux/virtio_mem.h:205:2: error: unknown type name 'uint64_t'
     uint64_t requested_size;
     ^

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 46585 bytes --]