From: kernel test robot <lkp@intel.com>
To: jasperwang@tencent.com, kaixuxia@tencent.com,
frankjpliu@tencent.com, kasong@tencent.com,
sagazchen@tencent.com, kernelxing@tencent.com,
aurelianliu@tencent.com, jason.zeng@intel.com,
wu.zheng@intel.com, yingbao.jia@intel.com, pei.p.jia@intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: drivers/iommu/rockchip-iommu.c:1130:26: error: initialization of 'void (*)(struct iommu_domain *, long unsigned int, size_t)' {aka 'void (*)(struct iommu_domain *, long unsigned int, long unsigned int)'} from incompatible pointer type 'void (*)(struct d...
Date: Fri, 8 Mar 2024 09:59:57 +0800 [thread overview]
Message-ID: <202403080959.bFCMsblt-lkp@intel.com> (raw)
tree: https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git linux-5.4/lts/5.4.119-20.0009.spr
head: e116ff64db9be38b70fd5b050f5900435d428547
commit: 2ba540b3e8ba5881d28dcd96874423009318eada iommu: Add iova and size as parameters in iotlb_sync_map
date: 9 months ago
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20240308/202403080959.bFCMsblt-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240308/202403080959.bFCMsblt-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/202403080959.bFCMsblt-lkp@intel.com/
Note: the opencloudos/linux-5.4/lts/5.4.119-20.0009.spr HEAD e116ff64db9be38b70fd5b050f5900435d428547 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
drivers/iommu/rockchip-iommu.c: In function 'rk_iommu_add_device':
drivers/iommu/rockchip-iommu.c:1069:17: error: implicit declaration of function 'iommu_group_get_for_dev'; did you mean 'iommu_group_get_by_id'? [-Werror=implicit-function-declaration]
1069 | group = iommu_group_get_for_dev(dev);
| ^~~~~~~~~~~~~~~~~~~~~~~
| iommu_group_get_by_id
drivers/iommu/rockchip-iommu.c:1069:15: warning: assignment to 'struct iommu_group *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1069 | group = iommu_group_get_for_dev(dev);
| ^
drivers/iommu/rockchip-iommu.c: At top level:
drivers/iommu/rockchip-iommu.c:1127:16: error: initialization of 'int (*)(struct iommu_domain *, long unsigned int, phys_addr_t, size_t, int, gfp_t)' {aka 'int (*)(struct iommu_domain *, long unsigned int, long long unsigned int, long unsigned int, int, unsigned int)'} from incompatible pointer type 'int (*)(struct iommu_domain *, long unsigned int, phys_addr_t, size_t, int)' {aka 'int (*)(struct iommu_domain *, long unsigned int, long long unsigned int, long unsigned int, int)'} [-Werror=incompatible-pointer-types]
1127 | .map = rk_iommu_map,
| ^~~~~~~~~~~~
drivers/iommu/rockchip-iommu.c:1127:16: note: (near initialization for 'rk_iommu_ops.map')
drivers/iommu/rockchip-iommu.c:1129:10: error: 'const struct iommu_ops' has no member named 'add_device'
1129 | .add_device = rk_iommu_add_device,
| ^~~~~~~~~~
drivers/iommu/rockchip-iommu.c:1129:23: error: initialization of 'void (*)(struct iommu_domain *)' from incompatible pointer type 'int (*)(struct device *)' [-Werror=incompatible-pointer-types]
1129 | .add_device = rk_iommu_add_device,
| ^~~~~~~~~~~~~~~~~~~
drivers/iommu/rockchip-iommu.c:1129:23: note: (near initialization for 'rk_iommu_ops.flush_iotlb_all')
drivers/iommu/rockchip-iommu.c:1130:10: error: 'const struct iommu_ops' has no member named 'remove_device'; did you mean 'probe_device'?
1130 | .remove_device = rk_iommu_remove_device,
| ^~~~~~~~~~~~~
| probe_device
>> drivers/iommu/rockchip-iommu.c:1130:26: error: initialization of 'void (*)(struct iommu_domain *, long unsigned int, size_t)' {aka 'void (*)(struct iommu_domain *, long unsigned int, long unsigned int)'} from incompatible pointer type 'void (*)(struct device *)' [-Werror=incompatible-pointer-types]
1130 | .remove_device = rk_iommu_remove_device,
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/iommu/rockchip-iommu.c:1130:26: note: (near initialization for 'rk_iommu_ops.iotlb_sync_map')
cc1: some warnings being treated as errors
vim +1130 drivers/iommu/rockchip-iommu.c
^590eaf1fec755 Kaixu Xia 2021-03-16 1121
^590eaf1fec755 Kaixu Xia 2021-03-16 1122 static const struct iommu_ops rk_iommu_ops = {
^590eaf1fec755 Kaixu Xia 2021-03-16 1123 .domain_alloc = rk_iommu_domain_alloc,
^590eaf1fec755 Kaixu Xia 2021-03-16 1124 .domain_free = rk_iommu_domain_free,
^590eaf1fec755 Kaixu Xia 2021-03-16 1125 .attach_dev = rk_iommu_attach_device,
^590eaf1fec755 Kaixu Xia 2021-03-16 1126 .detach_dev = rk_iommu_detach_device,
^590eaf1fec755 Kaixu Xia 2021-03-16 1127 .map = rk_iommu_map,
^590eaf1fec755 Kaixu Xia 2021-03-16 1128 .unmap = rk_iommu_unmap,
^590eaf1fec755 Kaixu Xia 2021-03-16 1129 .add_device = rk_iommu_add_device,
^590eaf1fec755 Kaixu Xia 2021-03-16 @1130 .remove_device = rk_iommu_remove_device,
^590eaf1fec755 Kaixu Xia 2021-03-16 1131 .iova_to_phys = rk_iommu_iova_to_phys,
^590eaf1fec755 Kaixu Xia 2021-03-16 1132 .device_group = rk_iommu_device_group,
^590eaf1fec755 Kaixu Xia 2021-03-16 1133 .pgsize_bitmap = RK_IOMMU_PGSIZE_BITMAP,
^590eaf1fec755 Kaixu Xia 2021-03-16 1134 .of_xlate = rk_iommu_of_xlate,
^590eaf1fec755 Kaixu Xia 2021-03-16 1135 };
^590eaf1fec755 Kaixu Xia 2021-03-16 1136
:::::: The code at line 1130 was first introduced by commit
:::::: 590eaf1fec755215547690e787cc7d83f58ea948 Init Repo base on linux 5.4.32 long term, and add base tlinux kernel interfaces.
:::::: TO: Kaixu Xia <kaixuxia@tencent.com>
:::::: CC: Kaixu Xia <kaixuxia@tencent.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-08 2:00 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=202403080959.bFCMsblt-lkp@intel.com \
--to=lkp@intel.com \
--cc=aurelianliu@tencent.com \
--cc=frankjpliu@tencent.com \
--cc=jason.zeng@intel.com \
--cc=jasperwang@tencent.com \
--cc=kaixuxia@tencent.com \
--cc=kasong@tencent.com \
--cc=kernelxing@tencent.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pei.p.jia@intel.com \
--cc=sagazchen@tencent.com \
--cc=wu.zheng@intel.com \
--cc=yingbao.jia@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.