From: kbuild test robot <lkp@intel.com>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: kbuild-all@01.org, iommu@lists.linux-foundation.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
joro@8bytes.org, jroedel@suse.de, alex.williamson@redhat.com,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH 1/2] iommu: Fix iommu_unmap and iommu_unmap_fast return type
Date: Sat, 3 Feb 2018 03:13:22 +0800 [thread overview]
Message-ID: <201802030258.SQALlbgq%fengguang.wu@intel.com> (raw)
In-Reply-To: <1517363285-89304-2-git-send-email-suravee.suthikulpanit@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2806 bytes --]
Hi Suravee,
I love your patch! Yet something to improve:
[auto build test ERROR on iommu/next]
[also build test ERROR on v4.15 next-20180202]
[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/Suravee-Suthikulpanit/iommu-Fix-iommu_unmap-and-iommu_unmap_fast-return-type/20180203-015316
base: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
config: s390-allyesconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=s390
All errors (new ones prefixed by >>):
>> drivers//iommu/s390-iommu.c:373:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.unmap = s390_iommu_unmap,
^~~~~~~~~~~~~~~~
drivers//iommu/s390-iommu.c:373:11: note: (near initialization for 's390_iommu_ops.unmap')
cc1: some warnings being treated as errors
vim +373 drivers//iommu/s390-iommu.c
f42c22351 Joerg Roedel 2017-04-27 365
cceb84519 Arvind Yadav 2017-08-28 366 static const struct iommu_ops s390_iommu_ops = {
8128f23c4 Gerald Schaefer 2015-08-27 367 .capable = s390_iommu_capable,
8128f23c4 Gerald Schaefer 2015-08-27 368 .domain_alloc = s390_domain_alloc,
8128f23c4 Gerald Schaefer 2015-08-27 369 .domain_free = s390_domain_free,
8128f23c4 Gerald Schaefer 2015-08-27 370 .attach_dev = s390_iommu_attach_device,
8128f23c4 Gerald Schaefer 2015-08-27 371 .detach_dev = s390_iommu_detach_device,
8128f23c4 Gerald Schaefer 2015-08-27 372 .map = s390_iommu_map,
8128f23c4 Gerald Schaefer 2015-08-27 @373 .unmap = s390_iommu_unmap,
8128f23c4 Gerald Schaefer 2015-08-27 374 .iova_to_phys = s390_iommu_iova_to_phys,
8128f23c4 Gerald Schaefer 2015-08-27 375 .add_device = s390_iommu_add_device,
8128f23c4 Gerald Schaefer 2015-08-27 376 .remove_device = s390_iommu_remove_device,
0929deca4 Joerg Roedel 2017-06-15 377 .device_group = generic_device_group,
8128f23c4 Gerald Schaefer 2015-08-27 378 .pgsize_bitmap = S390_IOMMU_PGSIZES,
8128f23c4 Gerald Schaefer 2015-08-27 379 };
8128f23c4 Gerald Schaefer 2015-08-27 380
:::::: The code at line 373 was first introduced by commit
:::::: 8128f23c436d0dd4f72412e1bf9256e424479dc3 iommu/s390: Add iommu api for s390 pci devices
:::::: TO: Gerald Schaefer <gerald.schaefer@de.ibm.com>
:::::: CC: Joerg Roedel <jroedel@suse.de>
---
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: 48730 bytes --]
next prev parent reply other threads:[~2018-02-02 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 1:48 [PATCH 0/2] iommu / vfio: Clean up iommu_map[_fast] interface Suravee Suthikulpanit
2018-01-31 1:48 ` [PATCH 1/2] iommu: Fix iommu_unmap and iommu_unmap_fast return type Suravee Suthikulpanit
2018-01-31 18:02 ` Robin Murphy
2018-02-01 5:03 ` Suravee Suthikulpanit
2018-02-01 12:17 ` Robin Murphy
2018-02-02 19:13 ` kbuild test robot [this message]
2018-02-02 19:41 ` kbuild test robot
2018-02-02 23:57 ` kbuild test robot
2018-01-31 1:48 ` [PATCH 2/2] vfio/type1: Add iommu_unmap error check when vfio_unmap_unpin Suravee Suthikulpanit
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=201802030258.SQALlbgq%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
/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®