From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
"Łukasz Bartosik" <ukaszb@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:dd-classmap-fix-8d 15/36] lib/dynamic_debug.c:1202:28: error: incomplete definition of type 'struct module'
Date: Thu, 23 May 2024 00:38:03 +0800 [thread overview]
Message-ID: <202405230018.cfDp0UI1-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git dd-classmap-fix-8d
head: 2352bebbccad8392205c384daaee21f2d9f23d8b
commit: afcb89e9541581d45c1619217f94aa8f80d19649 [15/36] dyndbg-API: fix DECLARE_DYNDBG_CLASSMAP
config: i386-buildonly-randconfig-002-20240522 (https://download.01.org/0day-ci/archive/20240523/202405230018.cfDp0UI1-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240523/202405230018.cfDp0UI1-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/oe-kbuild-all/202405230018.cfDp0UI1-lkp@intel.com/
All errors (new ones prefixed by >>):
>> lib/dynamic_debug.c:1202:28: error: incomplete definition of type 'struct module'
1202 | for (i = 0, kp = cm->mod->kp; i < cm->mod->num_kp; i++, kp++)
| ~~~~~~~^
arch/x86/include/asm/alternative.h:108:8: note: forward declaration of 'struct module'
108 | struct module;
| ^
lib/dynamic_debug.c:1202:45: error: incomplete definition of type 'struct module'
1202 | for (i = 0, kp = cm->mod->kp; i < cm->mod->num_kp; i++, kp++)
| ~~~~~~~^
arch/x86/include/asm/alternative.h:108:8: note: forward declaration of 'struct module'
108 | struct module;
| ^
2 errors generated.
vim +1202 lib/dynamic_debug.c
1193
1194 static void ddebug_apply_params(const struct ddebug_class_map *cm, const char *modnm)
1195 {
1196 const struct kernel_param *kp;
1197 int i;
1198
1199 if (IS_ENABLED(CONFIG_MODULES)) {
1200 if (cm->mod) {
1201 vpr_cm_info(cm, "loaded class:");
> 1202 for (i = 0, kp = cm->mod->kp; i < cm->mod->num_kp; i++, kp++)
1203 ddebug_match_apply_kparam(kp, cm, modnm);
1204 }
1205 }
1206 if (!cm->mod) {
1207 vpr_cm_info(cm, "builtin class:");
1208 for (kp = __start___param; kp < __stop___param; kp++)
1209 ddebug_match_apply_kparam(kp, cm, modnm);
1210 }
1211 }
1212
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-22 16:38 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=202405230018.cfDp0UI1-lkp@intel.com \
--to=lkp@intel.com \
--cc=jim.cromie@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ukaszb@chromium.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.