From: kernel test robot <lkp@intel.com>
To: Yi Liu <yi.l.liu@intel.com>, Kevin Tian <kevin.tian@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [yiliu1765-iommufd:wip/iommufd_pasid-20240910 19/37] drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:3044:19: error: incompatible function pointer types initializing 'int (*)(struct iommu_domain *, struct device *, ioasid_t, struct iommu_domain *)' (aka 'int (*)(struct iommu_domain *, struct device *, unsigned ...
Date: Wed, 11 Sep 2024 20:57:12 +0800 [thread overview]
Message-ID: <202409112006.YMXPT87F-lkp@intel.com> (raw)
tree: https://github.com/yiliu1765/iommufd.git wip/iommufd_pasid-20240910
head: 47bd94563684b36d40cac3c558ca963539dd5980
commit: 40f580261cf35cef57fc7ad2060f485e104a0967 [19/37] iommu/arm-smmu-v3: Make smmuv3 blocked domain support PASID
config: arm64-randconfig-002-20240911 (https://download.01.org/0day-ci/archive/20240911/202409112006.YMXPT87F-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240911/202409112006.YMXPT87F-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202409112006.YMXPT87F-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:3044:19: error: incompatible function pointer types initializing 'int (*)(struct iommu_domain *, struct device *, ioasid_t, struct iommu_domain *)' (aka 'int (*)(struct iommu_domain *, struct device *, unsigned int, struct iommu_domain *)') with an expression of type 'int (struct iommu_domain *, struct iommu_domain *, struct device *, ioasid_t)' (aka 'int (struct iommu_domain *, struct iommu_domain *, struct device *, unsigned int)') [-Werror,-Wincompatible-function-pointer-types]
.set_dev_pasid = arm_smmu_blocking_set_dev_pasid,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +3044 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
3041
3042 static const struct iommu_domain_ops arm_smmu_blocked_ops = {
3043 .attach_dev = arm_smmu_attach_dev_blocked,
> 3044 .set_dev_pasid = arm_smmu_blocking_set_dev_pasid,
3045 };
3046
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-11 12:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202409112006.YMXPT87F-lkp@intel.com \
--to=lkp@intel.com \
--cc=kevin.tian@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yi.l.liu@intel.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 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.