From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: scripts/mod/modpost.c:57:13: warning: variable 'extra_warn' set but not used
Date: Mon, 30 Mar 2026 08:15:32 +0800 [thread overview]
Message-ID: <202603300830.fbqcSGEA-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: llvm@lists.linux.dev
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
CC: Masahiro Yamada <masahiroy@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7aaa8047eafd0bd628065b15757d9b48c5f9c07d
commit: 6c6c1fc09de35f409f6971cb9e881103afe5dbe0 modpost: require a MODULE_DESCRIPTION()
date: 1 year ago
:::::: branch date: 86 minutes ago
:::::: commit date: 1 year ago
config: loongarch-allnoconfig (https://download.01.org/0day-ci/archive/20260330/202603300830.fbqcSGEA-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 054e11d1a17e5ba88bb1a8ef32fad3346e80b186)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260330/202603300830.fbqcSGEA-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/202603300830.fbqcSGEA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> scripts/mod/modpost.c:57:13: warning: variable 'extra_warn' set but not used [-Wunused-but-set-global]
57 | static bool extra_warn;
| ^
1 warning generated.
--
scripts/dtc/dtc-lexer.lex.c:630:12: warning: variable 'dts_version' set but not used [-Wunused-but-set-global]
630 | static int dts_version = 1;
| ^
1 warning generated.
scripts/sorttable.c:399:12: warning: variable 'long_size' set but not used [-Wunused-but-set-global]
399 | static int long_size;
| ^
1 warning generated.
>> scripts/mod/modpost.c:57:13: warning: variable 'extra_warn' set but not used [-Wunused-but-set-global]
57 | static bool extra_warn;
| ^
1 warning generated.
In file included from arch/loongarch/kernel/asm-offsets.c:12:
In file included from include/linux/kvm_host.h:45:
In file included from arch/loongarch/include/asm/kvm_host.h:20:
In file included from arch/loongarch/include/asm/kvm_mmu.h:11:
arch/loongarch/include/asm/tlb.h:142:24: warning: default initialization of an object of type 'struct vm_area_struct' with const member leaves the object uninitialized [-Wdefault-const-init-field-unsafe]
142 | struct vm_area_struct vma;
| ^
include/linux/mm_types.h:707:20: note: member 'vm_flags' declared 'const' here
707 | const vm_flags_t vm_flags;
| ^
1 warning generated.
vim +/extra_warn +57 scripts/mod/modpost.c
0fd3fbadd9a85e3 Masahiro Yamada 2020-12-01 56
20ff36856fe0087 Masahiro Yamada 2023-06-06 @57 static bool extra_warn;
20ff36856fe0087 Masahiro Yamada 2023-06-06 58
:::::: The code at line 57 was first introduced by commit
:::::: 20ff36856fe00879f82de71fe6f1482ca1b72334 modpost: propagate W=1 build option to modpost
:::::: TO: Masahiro Yamada <masahiroy@kernel.org>
:::::: CC: Masahiro Yamada <masahiroy@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-30 0:16 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=202603300830.fbqcSGEA-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox