From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [jimc:dd-fix-2i 14/18] drivers/gpu/drm/drm_print.c:72:1: sparse: sparse: symbol with external linkage has initializer
Date: Wed, 21 Jun 2023 22:33:35 +0800 [thread overview]
Message-ID: <202306212236.GVs74ID5-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check first_new_problem: drivers/gpu/drm/drm_print.c:72:1: sparse: sparse: symbol with external linkage has initializer"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Jim Cromie <jim.cromie@gmail.com>
Hi Jim,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://github.com/jimc/linux.git dd-fix-2i
head: 706822e871c197cefca034dce9582e0fc916732b
commit: ef232594f3c9aad7f5e0025231dc669570c3548a [14/18] drm: restore CONFIG_DRM_USE_DYNAMIC_DEBUG un-BROKEN
:::::: branch date: 19 hours ago
:::::: commit date: 19 hours ago
config: i386-randconfig-s002-20230620 (https://download.01.org/0day-ci/archive/20230621/202306212236.GVs74ID5-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230621/202306212236.GVs74ID5-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/r/202306212236.GVs74ID5-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/drm_print.c:72:1: sparse: sparse: symbol with external linkage has initializer
drivers/gpu/drm/drm_print.c:59:1: sparse: sparse: symbol 'drm_debug_classes_classnames' was not declared. Should it be static?
vim +72 drivers/gpu/drm/drm_print.c
f158936b60a787 Jim Cromie 2022-09-11 54
f158936b60a787 Jim Cromie 2022-09-11 55 #if !defined(CONFIG_DRM_USE_DYNAMIC_DEBUG)
f158936b60a787 Jim Cromie 2022-09-11 56 module_param_named(debug, __drm_debug, ulong, 0600);
f158936b60a787 Jim Cromie 2022-09-11 57 #else
164636c3874a28 Jim Cromie 2022-12-21 58 /* classnames must match value-symbols of enum drm_debug_category */
164636c3874a28 Jim Cromie 2022-12-21 59 DRM_CLASSMAP_DEFINE(drm_debug_classes, DD_CLASS_TYPE_DISJOINT_BITS,
164636c3874a28 Jim Cromie 2022-12-21 60 DRM_UT_CORE,
f158936b60a787 Jim Cromie 2022-09-11 61 "DRM_UT_CORE",
f158936b60a787 Jim Cromie 2022-09-11 62 "DRM_UT_DRIVER",
f158936b60a787 Jim Cromie 2022-09-11 63 "DRM_UT_KMS",
f158936b60a787 Jim Cromie 2022-09-11 64 "DRM_UT_PRIME",
f158936b60a787 Jim Cromie 2022-09-11 65 "DRM_UT_ATOMIC",
f158936b60a787 Jim Cromie 2022-09-11 66 "DRM_UT_VBL",
f158936b60a787 Jim Cromie 2022-09-11 67 "DRM_UT_STATE",
f158936b60a787 Jim Cromie 2022-09-11 68 "DRM_UT_LEASE",
f158936b60a787 Jim Cromie 2022-09-11 69 "DRM_UT_DP",
f158936b60a787 Jim Cromie 2022-09-11 70 "DRM_UT_DRMRES");
f158936b60a787 Jim Cromie 2022-09-11 71
c3109b624b9d04 Jim Cromie 2023-06-09 @72 DRM_CLASSMAP_PARAM_REF(debug, __drm_debug, drm_debug_classes, p);
c3109b624b9d04 Jim Cromie 2023-06-09 73
:::::: The code at line 72 was first introduced by commit
:::::: c3109b624b9d040f1002ae267886572688fd2d93 dyndbg-API: promote DYNDBG_CLASSMAP_PARAM to API
:::::: TO: Jim Cromie <jim.cromie@gmail.com>
:::::: CC: Jim Cromie <jim.cromie@gmail.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-21 14:34 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=202306212236.GVs74ID5-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.