From: kbuild test robot <lkp@intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: kbuild-all@01.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix crash when accessing VT-d sysfs entries
Date: Wed, 1 Mar 2017 09:06:26 +0800 [thread overview]
Message-ID: <201703010934.VmE2JkqM%fengguang.wu@intel.com> (raw)
In-Reply-To: <1488291019-13836-1-git-send-email-joro@8bytes.org>
[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]
Hi Joerg,
[auto build test ERROR on iommu/next]
[also build test ERROR on v4.10 next-20170228]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Joerg-Roedel/iommu-vt-d-Fix-crash-when-accessing-VT-d-sysfs-entries/20170301-074355
base: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
config: x86_64-randconfig-s1-03010801 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/i915/i915_drv.h:41,
from drivers/gpu/drm/i915/i915_drv.c:48:
include/linux/intel-iommu.h: In function 'dev_to_intel_iommu':
include/linux/intel-iommu.h:457: error: 'struct iommu_device' has no member named 'dev'
>> include/linux/intel-iommu.h:457: error: type defaults to 'int' in declaration of '__mptr'
cc1: warnings being treated as errors
>> include/linux/intel-iommu.h:457: error: initialization from incompatible pointer type
include/linux/intel-iommu.h:457: error: 'struct iommu_device' has no member named 'dev'
vim +457 include/linux/intel-iommu.h
451 if (!ecap_coherent(iommu->ecap))
452 clflush_cache_range(addr, size);
453 }
454
455 static inline struct intel_iommu *dev_to_intel_iommu(struct device *dev)
456 {
> 457 return container_of(dev, struct intel_iommu, iommu.dev);
458 }
459
460 extern struct dmar_drhd_unit * dmar_find_matched_drhd_unit(struct pci_dev *dev);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 21998 bytes --]
prev parent reply other threads:[~2017-03-01 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 14:10 Joerg Roedel
2017-02-28 14:10 ` [PATCH 2/2] iommu/amd: Fix crash when accessing AMD-Vi " Joerg Roedel
2017-03-01 0:19 ` [PATCH 1/2] iommu/vt-d: Fix crash when accessing VT-d " kbuild test robot
2017-03-01 10:01 ` Joerg Roedel
2017-03-01 1:06 ` kbuild test robot [this message]
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=201703010934.VmE2JkqM%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.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®