> -----Original Message----- > From: devel [mailto:driverdev-devel-bounces@xxxxxxxxxxxxxxxxxxxxxx] On > Behalf Of kbuild test robot > Sent: Thursday, December 8, 2016 1:50 AM > To: kys@xxxxxxxxxxxxxxxxxxxxxx > Cc: olaf@xxxxxxxxx; gregkh@xxxxxxxxxxxxxxxxxxx; jasowang@xxxxxxxxxx; > Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx; > bjorn.helgaas@xxxxxxxxx; kbuild-all@xxxxxx; apw@xxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxxxx; leann.ogasawara@xxxxxxxxxxxxx > Subject: Re: [PATCH 1/3] hyperv: Move hv_pci_dev and related structs to > hyperv.h > > Hi Haiyang, > > [auto build test ERROR on next-20161208] > [also build test ERROR on v4.9-rc8] > [cannot apply to linus/master linux/master pci/next v4.9-rc8 v4.9-rc7 v4.9- > rc6] > [if your patch is applied to the wrong git tree, please drop us a note to help > improve the system] > > url: > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub > .com%2F0day-ci%2Flinux%2Fcommits%2Fkys-exchange-microsoft- > com%2Fhyperv-Move-hv_pci_dev-and-related-structs-to-hyperv- > h%2F20161208- > 171643&data=02%7C01%7Ckys%40microsoft.com%7Ca000870068f645a67492 > 08d41f4fa963%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6361678 > 75686353145&sdata=2cR2dMEa6sjz94NYUFMx5qC8hEVvXF6uokmCCny%2FgL > E%3D&reserved=0 > config: x86_64-randconfig-x012-201649 (attached as .config) > compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 > reproduce: > # save the attached .config to linux build tree > make ARCH=x86_64 > > All errors (new ones prefixed by >>): > > In file included from drivers/hid/hid-hyperv.c:22:0: > >> include/linux/hyperv.h:1660:25: error: field 'msi_info' has incomplete type > struct msi_domain_info msi_info; > ^~~~~~~~ > > vim +/msi_info +1660 include/linux/hyperv.h > > 1654 struct semaphore enum_sem; > 1655 struct list_head resources_for_children; > 1656 > 1657 struct list_head children; > 1658 struct list_head dr_list; > 1659 > > 1660 struct msi_domain_info msi_info; > 1661 struct msi_controller msi_chip; > 1662 struct irq_domain *irq_domain; > 1663 }; > Greg, I sent this patch set to show how we plan to use the API to check if a device is a VMBUS device. Given that multiple trees are involved, the patches were based on the linux-next tree. I was planning on submitting these patches with minimal inter-tree dependency. Regards, K. Y > --- > 0-DAY kernel test infrastructure Open Source Technology Center > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.01 > .org%2Fpipermail%2Fkbuild- > all&data=02%7C01%7Ckys%40microsoft.com%7Ca000870068f645a6749208d4 > 1f4fa963%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63616787568 > 6353145&sdata=5T776prLOj7qzsQa%2B3Giit1UFvZJ6D%2FdL0I8k1qKfIg%3D&r > eserved=0 Intel Corporation _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
