From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [jimc:dd-drm-next 5/8] drivers/gpu/drm/drm_print.c:60:1: error: too many arguments provided to function-like macro invocation
Date: Mon, 30 Aug 2021 10:51:22 +0800 [thread overview]
Message-ID: <202108301013.x8ixk2Ks-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3973 bytes --]
tree: https://github.com/jimc/linux.git dd-drm-next
head: 1ec0a417a3517114e1969e3b069576313350964b
commit: 974c56a9f5ebef9d2382c79d2b29afa5900b2289 [5/8] drm_print: add choice to use dynamic debug in drm-debug
config: arm64-buildonly-randconfig-r003-20210829 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 510e106fa8635e7f9c51c896180b971de6309b2f)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://github.com/jimc/linux/commit/974c56a9f5ebef9d2382c79d2b29afa5900b2289
git remote add jimc https://github.com/jimc/linux.git
git fetch --no-tags jimc dd-drm-next
git checkout 974c56a9f5ebef9d2382c79d2b29afa5900b2289
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/gpu/drm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
>> drivers/gpu/drm/drm_print.c:60:1: error: too many arguments provided to function-like macro invocation
DEFINE_DYNAMIC_DEBUG_CATEGORIES(debug, __drm_debug,
^
include/linux/dynamic_debug.h:283:12: note: expanded from macro 'DEFINE_DYNAMIC_DEBUG_CATEGORIES'
BUILD_BUG("DYNAMIC_DEBUG support required to use this macro: " #var)
^
include/linux/build_bug.h:59:9: note: macro 'BUILD_BUG' defined here
#define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
^
drivers/gpu/drm/drm_print.c:60:1: warning: declaration specifier missing, defaulting to 'int'
DEFINE_DYNAMIC_DEBUG_CATEGORIES(debug, __drm_debug,
^
int
include/linux/dynamic_debug.h:283:2: note: expanded from macro 'DEFINE_DYNAMIC_DEBUG_CATEGORIES'
BUILD_BUG("DYNAMIC_DEBUG support required to use this macro: " #var)
^
1 warning and 1 error generated.
--
>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_debug.c:66:1: error: too many arguments provided to function-like macro invocation
DEFINE_DYNAMIC_DEBUG_CATEGORIES(debug_dc, __debug_dc,
^
include/linux/dynamic_debug.h:283:12: note: expanded from macro 'DEFINE_DYNAMIC_DEBUG_CATEGORIES'
BUILD_BUG("DYNAMIC_DEBUG support required to use this macro: " #var)
^
include/linux/build_bug.h:59:9: note: macro 'BUILD_BUG' defined here
#define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
^
>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_debug.c:66:1: warning: declaration specifier missing, defaulting to 'int'
DEFINE_DYNAMIC_DEBUG_CATEGORIES(debug_dc, __debug_dc,
^
int
include/linux/dynamic_debug.h:283:2: note: expanded from macro 'DEFINE_DYNAMIC_DEBUG_CATEGORIES'
BUILD_BUG("DYNAMIC_DEBUG support required to use this macro: " #var)
^
1 warning and 1 error generated.
vim +60 drivers/gpu/drm/drm_print.c
57
58 #ifdef CONFIG_DRM_USE_DYNAMIC_DEBUG
59 #include <linux/dynamic_debug.h>
> 60 DEFINE_DYNAMIC_DEBUG_CATEGORIES(debug, __drm_debug,
61 DRM_DEBUG_DESC,
62 _DD_cat_(DRM_DBG_CAT_CORE),
63 _DD_cat_(DRM_DBG_CAT_DRIVER),
64 _DD_cat_(DRM_DBG_CAT_KMS),
65 _DD_cat_(DRM_DBG_CAT_PRIME),
66 _DD_cat_(DRM_DBG_CAT_ATOMIC),
67 _DD_cat_(DRM_DBG_CAT_VBL),
68 _DD_cat_(DRM_DBG_CAT_STATE),
69 _DD_cat_(DRM_DBG_CAT_LEASE),
70 _DD_cat_(DRM_DBG_CAT_DP),
71 _DD_cat_(DRM_DBG_CAT_DRMRES));
72
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 48230 bytes --]
reply other threads:[~2021-08-30 2:51 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=202108301013.x8ixk2Ks-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.