From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [luxis1999-iommufd:iommufd-v5.16-rc2 18/50] drivers/gpu/drm/tegra/drm.c:974:17: error: implicit declaration of function 'iommu_detatch_device'; did you mean 'iommu_detach_device'?
Date: Sun, 28 Nov 2021 03:16:28 +0800 [thread overview]
Message-ID: <202111280324.l3kGUbgS-lkp@intel.com> (raw)
tree: https://github.com/luxis1999/iommufd iommufd-v5.16-rc2
head: 9821bacf94cee7dd38c9f919a0a38fd48a6f3ae7
commit: 7011c70a936e99eea5c03c44e03e359b1bd58de6 [18/50] drm/tegra: Use the iommu dma_owner mechanism
config: arm-defconfig (https://download.01.org/0day-ci/archive/20211128/202111280324.l3kGUbgS-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/luxis1999/iommufd/commit/7011c70a936e99eea5c03c44e03e359b1bd58de6
git remote add luxis1999-iommufd https://github.com/luxis1999/iommufd
git fetch --no-tags luxis1999-iommufd iommufd-v5.16-rc2
git checkout 7011c70a936e99eea5c03c44e03e359b1bd58de6
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/tegra/drm.c: In function 'host1x_client_iommu_detach':
>> drivers/gpu/drm/tegra/drm.c:974:17: error: implicit declaration of function 'iommu_detatch_device'; did you mean 'iommu_detach_device'? [-Werror=implicit-function-declaration]
974 | iommu_detatch_device(tegra->domain, client->dev);
| ^~~~~~~~~~~~~~~~~~~~
| iommu_detach_device
cc1: some warnings being treated as errors
vim +974 drivers/gpu/drm/tegra/drm.c
962
963 void host1x_client_iommu_detach(struct host1x_client *client)
964 {
965 struct iommu_domain *domain = iommu_get_domain_for_dev(client->dev);
966 struct drm_device *drm = dev_get_drvdata(client->host);
967 struct tegra_drm *tegra = drm->dev_private;
968
969 if (domain && domain != tegra->domain)
970 return iommu_device_release_dma_owner(client->dev,
971 DMA_OWNER_DMA_API);
972
973 if (client->group) {
> 974 iommu_detatch_device(tegra->domain, client->dev);
975 client->group = NULL;
976 }
977 }
978
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-11-27 19:19 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=202111280324.l3kGUbgS-lkp@intel.com \
--to=lkp@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.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®