From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:incoming-android15-6.6-desktop-chromeos 499/499] drivers/dma-buf/heaps/restricted_heap.c:201:14: error: incompatible function pointer types initializing 'struct dma_buf *(*)(struct dma_heap *, unsigned long, u32, u64)' (aka 'struct dma_buf *(*)(struct dma_heap *, unsigned long, unsigned int, unsigned lo...
Date: Fri, 28 Mar 2025 22:38:48 +0800 [thread overview]
Message-ID: <202503282220.7gglddWC-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common incoming-android15-6.6-desktop-chromeos
head: 05387f6649b8b2e90387b0f30e788b96413e54d0
commit: 05387f6649b8b2e90387b0f30e788b96413e54d0 [499/499] Revert "FROMLIST: dma-buf: system_heap: Add a system-uncached heap re-using the system heap"
config: x86_64-buildonly-randconfig-002-20250328 (https://download.01.org/0day-ci/archive/20250328/202503282220.7gglddWC-lkp@intel.com/config)
compiler: clang version 20.1.1 (https://github.com/llvm/llvm-project 424c2d9b7e4de40d0804dd374721e6411c27d1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250328/202503282220.7gglddWC-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/202503282220.7gglddWC-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/dma-buf/heaps/restricted_heap.c:201:14: error: incompatible function pointer types initializing 'struct dma_buf *(*)(struct dma_heap *, unsigned long, u32, u64)' (aka 'struct dma_buf *(*)(struct dma_heap *, unsigned long, unsigned int, unsigned long long)') with an expression of type 'struct dma_buf *(struct dma_heap *, unsigned long, unsigned long, unsigned long)' [-Wincompatible-function-pointer-types]
201 | .allocate = restricted_heap_allocate,
| ^~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +201 drivers/dma-buf/heaps/restricted_heap.c
7250c068a51cbf4 Yong Wu 2024-05-15 199
7250c068a51cbf4 Yong Wu 2024-05-15 200 static const struct dma_heap_ops rheap_ops = {
7250c068a51cbf4 Yong Wu 2024-05-15 @201 .allocate = restricted_heap_allocate,
7250c068a51cbf4 Yong Wu 2024-05-15 202 };
7250c068a51cbf4 Yong Wu 2024-05-15 203
:::::: The code at line 201 was first introduced by commit
:::::: 7250c068a51cbf472372ddd41d02087ccab05175 FROMLIST: dma-buf: heaps: Initialize a restricted heap
:::::: TO: Yong Wu <yong.wu@mediatek.com>
:::::: CC: Hubert Mazur <hmazur@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-28 14:39 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=202503282220.7gglddWC-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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 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.