From: kbuild test robot <lkp@intel.com>
To: Keith Busch <keith.busch@intel.com>
Cc: kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, linux-pci@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Dan Williams <dan.j.williams@intel.com>,
Bryan Veal <bryan.e.veal@intel.com>,
Jon Derrick <jonathan.derrick@intel.com>,
Keith Busch <keith.busch@intel.com>
Subject: Re: [PATCHv8] x86/PCI: Initial commit for new VMD device driver
Date: Wed, 13 Jan 2016 01:40:33 +0800 [thread overview]
Message-ID: <201601130151.Y87x1uES%fengguang.wu@intel.com> (raw)
In-Reply-To: <1452616119-11450-2-git-send-email-keith.busch@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
Hi Keith,
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.4 next-20160112]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Keith-Busch/x86-PCI-Initial-commit-for-new-VMD-device-driver/20160113-003207
config: x86_64-allmodconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> arch/x86/pci/vmd.c:85:20: error: field 'dma_domain' has incomplete type
struct dma_domain dma_domain;
^
arch/x86/pci/vmd.c: In function 'vmd_teardown_dma_ops':
>> arch/x86/pci/vmd.c:372:3: error: implicit declaration of function 'del_dma_domain' [-Werror=implicit-function-declaration]
del_dma_domain(domain);
^
arch/x86/pci/vmd.c: In function 'vmd_setup_dma_ops':
>> arch/x86/pci/vmd.c:387:8: error: dereferencing pointer to incomplete type 'struct dma_domain'
domain->domain_nr = vmd->sysdata.domain;
^
>> arch/x86/pci/vmd.c:409:2: error: implicit declaration of function 'add_dma_domain' [-Werror=implicit-function-declaration]
add_dma_domain(domain);
^
arch/x86/pci/vmd.c: In function 'vmd_enable_domain':
arch/x86/pci/vmd.c:559:2: error: implicit declaration of function 'dev_set_msi_domain' [-Werror=implicit-function-declaration]
dev_set_msi_domain(&vmd->bus->dev, vmd->irq_domain);
^
cc1: some warnings being treated as errors
vim +/dma_domain +85 arch/x86/pci/vmd.c
79 struct resource resources[3];
80 struct irq_domain *irq_domain;
81 struct pci_bus *bus;
82
83 #ifdef CONFIG_X86_DEV_DMA_OPS
84 struct dma_map_ops dma_ops;
> 85 struct dma_domain dma_domain;
86 #endif
87 };
88
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 48920 bytes --]
next prev parent reply other threads:[~2016-01-12 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 16:28 [PATCHv8] Driver for new "VMD" device Keith Busch
2016-01-12 16:28 ` [PATCHv8] x86/PCI: Initial commit for new VMD device driver Keith Busch
2016-01-12 17:40 ` kbuild test robot [this message]
2016-01-12 18:08 ` Keith Busch
2016-01-12 19:42 ` Bjorn Helgaas
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=201601130151.Y87x1uES%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bhelgaas@google.com \
--cc=bryan.e.veal@intel.com \
--cc=dan.j.williams@intel.com \
--cc=jonathan.derrick@intel.com \
--cc=kbuild-all@01.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®