From: KY Srinivasan <kys@microsoft.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: kbuild test robot <lkp@intel.com>,
"kys@exchange.microsoft.com" <kys@exchange.microsoft.com>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"jasowang@redhat.com" <jasowang@redhat.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bjorn.helgaas@gmail.com" <bjorn.helgaas@gmail.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"apw@canonical.com" <apw@canonical.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"leann.ogasawara@canonical.com" <leann.ogasawara@canonical.com>
Subject: RE: [PATCH 1/3] hyperv: Move hv_pci_dev and related structs to hyperv.h
Date: Thu, 8 Dec 2016 16:54:55 +0000 [thread overview]
Message-ID: <BN6PR03MB24814478ACE17A437793D887A0840@BN6PR03MB2481.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20161208155656.GB4601@kroah.com>
> -----Original Message-----
> From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> Sent: Thursday, December 8, 2016 7:57 AM
> To: KY Srinivasan <kys@microsoft.com>
> Cc: kbuild test robot <lkp@intel.com>; kys@exchange.microsoft.com;
> olaf@aepfle.de; jasowang@redhat.com; Haiyang Zhang
> <haiyangz@microsoft.com>; linux-kernel@vger.kernel.org;
> bjorn.helgaas@gmail.com; kbuild-all@01.org; apw@canonical.com;
> devel@linuxdriverproject.org; leann.ogasawara@canonical.com
> Subject: Re: [PATCH 1/3] hyperv: Move hv_pci_dev and related structs to
> hyperv.h
>
> On Thu, Dec 08, 2016 at 03:26:06PM +0000, KY Srinivasan wrote:
> >
> >
> > > -----Original Message-----
> > > From: devel [mailto:driverdev-devel-bounces@linuxdriverproject.org]
> On
> > > Behalf Of kbuild test robot
> > > Sent: Thursday, December 8, 2016 1:50 AM
> > > To: kys@exchange.microsoft.com
> > > Cc: olaf@aepfle.de; gregkh@linuxfoundation.org;
> jasowang@redhat.com;
> > > Haiyang Zhang <haiyangz@microsoft.com>; linux-
> kernel@vger.kernel.org;
> > > bjorn.helgaas@gmail.com; kbuild-all@01.org; apw@canonical.com;
> > > devel@linuxdriverproject.org; leann.ogasawara@canonical.com
> > > 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.
>
> Ok, but how does this simple patch fail so badly? Maybe just wait for
> after 4.10-rc1 is out and then try this as everything will be synced up
> then? It's pretty much past the merge window for all subsystems now
> anyway...
Will do.
Thanks,
K. Y
next prev parent reply other threads:[~2016-12-08 16:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 8:33 [PATCH 0/3] Drivers: hv: Implement VF association based on serial number kys
2016-12-08 8:33 ` [PATCH 1/3] hyperv: Move hv_pci_dev and related structs to hyperv.h kys
2016-12-08 8:33 ` [PATCH 2/3] hyperv: Add a function to detect if the device is a vmbus dev kys
2016-12-08 8:33 ` [PATCH 3/3] hv_netvsc: Implement VF matching based on serial numbers kys
2016-12-08 15:56 ` Greg KH
2016-12-09 0:05 ` KY Srinivasan
2016-12-09 7:31 ` Greg KH
2016-12-09 18:20 ` Stephen Hemminger
2016-12-09 20:09 ` Haiyang Zhang
2016-12-09 20:29 ` Stephen Hemminger
2016-12-09 21:31 ` Haiyang Zhang
2016-12-09 21:45 ` Stephen Hemminger
2016-12-09 21:53 ` Haiyang Zhang
2016-12-09 22:05 ` Stephen Hemminger
2016-12-09 22:35 ` Haiyang Zhang
2016-12-10 0:21 ` Stephen Hemminger
2016-12-10 12:20 ` Greg KH
2016-12-14 23:18 ` Haiyang Zhang
2016-12-14 23:27 ` Greg KH
2016-12-14 23:51 ` Stephen Hemminger
2016-12-16 1:11 ` KY Srinivasan
2016-12-16 15:20 ` Haiyang Zhang
2016-12-16 18:39 ` KY Srinivasan
2016-12-16 16:45 ` Greg KH
2016-12-08 9:49 ` [PATCH 1/3] hyperv: Move hv_pci_dev and related structs to hyperv.h kbuild test robot
2016-12-08 15:26 ` KY Srinivasan
2016-12-08 15:56 ` gregkh
2016-12-08 16:54 ` KY Srinivasan [this message]
2016-12-08 11:15 ` kbuild test robot
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=BN6PR03MB24814478ACE17A437793D887A0840@BN6PR03MB2481.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=bjorn.helgaas@gmail.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@01.org \
--cc=kys@exchange.microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=olaf@aepfle.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.