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 501/501] drivers/dma-buf/heaps/cma_heap.c:368:21: error: initialization of 'struct dma_buf * (*)(struct dma_heap *, long unsigned int, long unsigned int, long unsigned int)' from incompatible pointer type 'struct dma_buf * (*)(struct dma_heap *, long unsigned in...
Date: Thu, 27 Mar 2025 05:42:33 +0800 [thread overview]
Message-ID: <202503270529.MELEUvvf-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common incoming-android15-6.6-desktop-chromeos
head: 762a13f385d861193f9d810f84780bdd56146d74
commit: 2e1af5fe2d41e093501194f1048cca6d79cb27b6 [501/501] FROMLIST: dma-buf: system_heap: Add a system-uncached heap re-using the system heap
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20250327/202503270529.MELEUvvf-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250327/202503270529.MELEUvvf-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/202503270529.MELEUvvf-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/dma-buf/heaps/cma_heap.c:368:21: error: initialization of 'struct dma_buf * (*)(struct dma_heap *, long unsigned int, long unsigned int, long unsigned int)' from incompatible pointer type 'struct dma_buf * (*)(struct dma_heap *, long unsigned int, u32, u64)' {aka 'struct dma_buf * (*)(struct dma_heap *, long unsigned int, unsigned int, long long unsigned int)'} [-Werror=incompatible-pointer-types]
368 | .allocate = cma_heap_allocate,
| ^~~~~~~~~~~~~~~~~
drivers/dma-buf/heaps/cma_heap.c:368:21: note: (near initialization for 'cma_heap_ops.allocate')
cc1: some warnings being treated as errors
vim +368 drivers/dma-buf/heaps/cma_heap.c
b61614ec318aae0 John Stultz 2019-12-03 366
b61614ec318aae0 John Stultz 2019-12-03 367 static const struct dma_heap_ops cma_heap_ops = {
b61614ec318aae0 John Stultz 2019-12-03 @368 .allocate = cma_heap_allocate,
b61614ec318aae0 John Stultz 2019-12-03 369 };
b61614ec318aae0 John Stultz 2019-12-03 370
:::::: The code at line 368 was first introduced by commit
:::::: b61614ec318aae0c77ecd2816878d851dd61d9a6 dma-buf: heaps: Add CMA heap to dmabuf heaps
:::::: TO: John Stultz <john.stultz@linaro.org>
:::::: CC: Sumit Semwal <sumit.semwal@linaro.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-26 21:43 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=202503270529.MELEUvvf-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.