From: kernel test robot <lkp@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [kuba:dma 2/11] drivers/xen/swiotlb-xen.c:435:11: error: incompatible function pointer types initializing 'void *(*)(struct device *, size_t, dma_addr_t *, gfp_t, unsigned long)' (aka 'void *(*)(struct device *, unsigned long, unsigned long long *, unsigned int, unsigned...
Date: Sat, 31 Oct 2026 04:11:45 +0100 [thread overview]
Message-ID: <202610310459.Y3UJp0xu-lkp@intel.com> (raw)
Hi Jakub,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kuba/linux.git dma
head: cd9029ebe3033a797c066b493e4cfcf5337cf829
commit: 40f9c52cdcf8713402ec7a31c47511d06bdcf5d2 [2/11] dma-direct: pass the NUMA node to dma_direct_alloc()
config: arm64-randconfig-2000-20261031 (https://download.01.org/0day-ci/archive/20261031/202610310459.Y3UJp0xu-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 8f6b51ca8bab1d49006ddaa042bc7e4e7306975d)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261031/202610310459.Y3UJp0xu-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/202610310459.Y3UJp0xu-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/xen/swiotlb-xen.c:435:11: error: incompatible function pointer types initializing 'void *(*)(struct device *, size_t, dma_addr_t *, gfp_t, unsigned long)' (aka 'void *(*)(struct device *, unsigned long, unsigned long long *, unsigned int, unsigned long)') with an expression of type 'void *(struct device *, size_t, dma_addr_t *, gfp_t, unsigned long, int)' (aka 'void *(struct device *, unsigned long, unsigned long long *, unsigned int, unsigned long, int)') [-Wincompatible-function-pointer-types]
435 | .alloc = dma_direct_alloc,
| ^~~~~~~~~~~~~~~~
1 error generated.
vim +435 drivers/xen/swiotlb-xen.c
eb1ddc00b81cb8 Stefano Stabellini 2013-10-09 429
dceb1a6819ab2c Christoph Hellwig 2017-05-21 430 const struct dma_map_ops xen_swiotlb_dma_ops = {
566fb90e050dfa Christoph Hellwig 2022-04-22 431 #ifdef CONFIG_X86
dceb1a6819ab2c Christoph Hellwig 2017-05-21 432 .alloc = xen_swiotlb_alloc_coherent,
dceb1a6819ab2c Christoph Hellwig 2017-05-21 433 .free = xen_swiotlb_free_coherent,
566fb90e050dfa Christoph Hellwig 2022-04-22 434 #else
566fb90e050dfa Christoph Hellwig 2022-04-22 @435 .alloc = dma_direct_alloc,
:::::: The code at line 435 was first introduced by commit
:::::: 566fb90e050dfa2132340bbdab9533b727dda6f1 swiotlb-xen: fix DMA_ATTR_NO_KERNEL_MAPPING on arm
:::::: TO: Christoph Hellwig <hch@lst.de>
:::::: CC: Christoph Hellwig <hch@lst.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-31 3:12 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=202610310459.Y3UJp0xu-lkp@intel.com \
--to=lkp@intel.com \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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