Hi all. On Sun, Jan 22, 2023 at 07:19:15AM +0800, kernel test robot wrote: > Hi Sam, > > I love your patch! Yet something to improve: > > [auto build test ERROR on 2e337a8d14bd4b04913d52ccf076be29d846acd7] > > url: https://github.com/intel-lab-lkp/linux/commits/Sam-Ravnborg-via-B4-Submission-Endpoint/drm-komeda-Direct-include-headers-from-drm_print/20230122-041306 > base: 2e337a8d14bd4b04913d52ccf076be29d846acd7 > patch link: https://lore.kernel.org/r/20230113-drm-include-v1-v1-16-c5cf72d8a5a2%40ravnborg.org > patch subject: [PATCH 16/86] drm/drm_print: Minimize include footprint > config: i386-randconfig-a004 (https://download.01.org/0day-ci/archive/20230122/202301220750.HzZm1ZHu-lkp@xxxxxxxxx/config) > compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1) > reproduce (this is a W=1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # https://github.com/intel-lab-lkp/linux/commit/530d852970d1a75527031a4f23689f89f0a85804 > git remote add linux-review https://github.com/intel-lab-lkp/linux > git fetch --no-tags linux-review Sam-Ravnborg-via-B4-Submission-Endpoint/drm-komeda-Direct-include-headers-from-drm_print/20230122-041306 > git checkout 530d852970d1a75527031a4f23689f89f0a85804 > # save the config file > mkdir build_dir && cp config build_dir/.config > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 olddefconfig > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash > > If you fix the issue, kindly add following tag where applicable > | Reported-by: kernel test robot <lkp@xxxxxxxxx> > > All errors (new ones prefixed by >>): > > >> drivers/gpu/drm/drm_mode_object.c:195:3: error: implicit declaration of function '_dynamic_func_call_cls' is invalid in C99 [-Werror,-Wimplicit-function-declaration] > DRM_DEBUG("OBJ ID: %d (%d)\n", obj->id, kref_read(&obj->refcount)); > ^ For anyone following this. I failed to reproduce the error below using the instructions above. It looks like some obscure combination of CONFIG options that may be unrelated to this patch. allmodconfig, allyesconfig for i386 did not trigger the bug. I will get back to this in a few days (maybe first in the weekend), and will share my findings. Sam
