[Intel-gfx] [PATCH 17/22] dma-buf: Proxy fence, an unsignaled fence placeholder
kbuild test robot
lkp at intel.com
Tue Mar 3 16:24:36 UTC 2020
Hi Chris,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[cannot apply to drm-tip/drm-tip linus/master v5.6-rc4 next-20200303]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-gem-Consolidate-ctx-engines-release/20200302-174042
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (git://gitmirror/llvm_project 211fb91f1067ecdf7c0b8a019bcf76554d813129)
reproduce:
# FIXME the reproduce steps for clang is not ready yet
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp at intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/dma-buf/dma-fence.c:22:
>> drivers/dma-buf/dma-fence-private.h:13:9: warning: 'DMA_FENCE_PRIVATE_H' is used as a header guard here, followed by #define of a different macro [-Wheader-guard]
#ifndef DMA_FENCE_PRIVATE_H
^~~~~~~~~~~~~~~~~~~
drivers/dma-buf/dma-fence-private.h:14:9: note: 'DMA_FENCE_PRIAVTE_H' is defined here; did you mean 'DMA_FENCE_PRIVATE_H'?
#define DMA_FENCE_PRIAVTE_H
^~~~~~~~~~~~~~~~~~~
DMA_FENCE_PRIVATE_H
1 warning generated.
vim +/DMA_FENCE_PRIVATE_H +13 drivers/dma-buf/dma-fence-private.h
> 13 #ifndef DMA_FENCE_PRIVATE_H
14 #define DMA_FENCE_PRIAVTE_H
15
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 72283 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/intel-gfx/attachments/20200304/1170508e/attachment-0001.gz>
More information about the Intel-gfx
mailing list