[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202309111534.u4wfJ4vk-lkp@intel.com>
Date: Mon, 11 Sep 2023 16:05:45 +0800
From: kernel test robot <lkp@...el.com>
To: Yong Wu <yong.wu@...iatek.com>, Rob Herring <robh+dt@...nel.org>,
Sumit Semwal <sumit.semwal@...aro.org>,
christian.koenig@....com, Matthias Brugger <matthias.bgg@...il.com>
Cc: oe-kbuild-all@...ts.linux.dev, devicetree@...r.kernel.org,
Conor Dooley <conor+dt@...nel.org>, jianjiao.zeng@...iatek.com,
Benjamin Gaignard <benjamin.gaignard@...labora.com>,
kuohong.wang@...iatek.com, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org, tjmercier@...gle.com,
linaro-mm-sig@...ts.linaro.org, John Stultz <jstultz@...gle.com>,
linux-arm-kernel@...ts.infradead.org,
Krzysztof Kozlowski <krzk@...nel.org>,
linux-mediatek@...ts.infradead.org, linux-media@...r.kernel.org,
Yong Wu <yong.wu@...iatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH 4/9] dma-buf: heaps: Initialise MediaTek secure heap
Hi Yong,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on robh/for-next linus/master v6.6-rc1 next-20230911]
[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/Yong-Wu/dma-buf-heaps-Deduplicate-docs-and-adopt-common-format/20230911-103308
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230911023038.30649-5-yong.wu%40mediatek.com
patch subject: [PATCH 4/9] dma-buf: heaps: Initialise MediaTek secure heap
config: openrisc-allmodconfig (https://download.01.org/0day-ci/archive/20230911/202309111534.u4wfJ4vk-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230911/202309111534.u4wfJ4vk-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309111534.u4wfJ4vk-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/dma-buf/heaps/mtk_secure_heap.c:68:27: 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 *, size_t, long unsigned int, long unsigned int)' {aka 'struct dma_buf * (*)(struct dma_heap *, unsigned int, long unsigned int, long unsigned int)'} [-Werror=incompatible-pointer-types]
68 | .allocate = mtk_sec_heap_allocate,
| ^~~~~~~~~~~~~~~~~~~~~
drivers/dma-buf/heaps/mtk_secure_heap.c:68:27: note: (near initialization for 'mtk_sec_heap_ops.allocate')
cc1: some warnings being treated as errors
vim +68 drivers/dma-buf/heaps/mtk_secure_heap.c
66
67 static const struct dma_heap_ops mtk_sec_heap_ops = {
> 68 .allocate = mtk_sec_heap_allocate,
69 };
70
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists