From: kernel test robot <lkp@intel.com>
To: Sachin Parekh <sachinparekh@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] driver core: platform: Call iommu_release_device in dma_cleanup
Date: Sun, 1 Sep 2024 21:28:16 +0800 [thread overview]
Message-ID: <202409012112.6WITFrsU-lkp@intel.com> (raw)
In-Reply-To: <20240829120504.2976612-1-sachinparekh@google.com>
Hi Sachin,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on driver-core/driver-core-next driver-core/driver-core-linus linus/master v6.11-rc6 next-20240830]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Sachin-Parekh/driver-core-platform-Call-iommu_release_device-in-dma_cleanup/20240829-200729
base: driver-core/driver-core-testing
patch link: https://lore.kernel.org/r/20240829120504.2976612-1-sachinparekh%40google.com
patch subject: [RFC PATCH] driver core: platform: Call iommu_release_device in dma_cleanup
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20240901/202409012112.6WITFrsU-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240901/202409012112.6WITFrsU-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/202409012112.6WITFrsU-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/base/platform.c: In function 'platform_dma_cleanup':
>> drivers/base/platform.c:1472:17: error: implicit declaration of function 'iommu_release_device'; did you mean 'iommu_detach_device'? [-Wimplicit-function-declaration]
1472 | iommu_release_device(dev);
| ^~~~~~~~~~~~~~~~~~~~
| iommu_detach_device
vim +1472 drivers/base/platform.c
1463
1464 static void platform_dma_cleanup(struct device *dev)
1465 {
1466 struct platform_driver *drv = to_platform_driver(dev->driver);
1467
1468 if (!drv->driver_managed_dma)
1469 iommu_device_unuse_default_domain(dev);
1470
1471 if (dev_of_node(dev))
> 1472 iommu_release_device(dev);
1473 }
1474
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-01 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 12:05 [RFC PATCH] driver core: platform: Call iommu_release_device in dma_cleanup Sachin Parekh
2024-08-29 13:52 ` Greg KH
2024-09-02 6:44 ` Sachin Parekh
2024-08-29 13:58 ` Robin Murphy
2024-09-02 6:17 ` Sachin Parekh
2024-09-01 13:28 ` kernel test robot [this message]
2024-09-01 13:49 ` kernel test robot
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=202409012112.6WITFrsU-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sachinparekh@google.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.