From: kernel test robot <lkp@intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [linux-stable-rc:linux-5.4.y 1142/1473] drivers/staging/wilc1000/wilc_wfi_cfgoperations.c:61:42: warning: unused variable 'wowlan_support'
Date: Tue, 31 Aug 2021 14:40:54 +0800 [thread overview]
Message-ID: <202108311442.hiXBftay-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2641 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
head: e32f4fa1b24d825b2560ca9cfbfd9df44a4310b4
commit: 62353048e2d4e398cfc22dbee3e1a7f6f535dcc1 [1142/1473] kbuild: support LLVM=1 to switch the default tools to Clang/LLVM
config: hexagon-randconfig-r045-20210830 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 4b1fde8a2b681dad2ce0c082a5d6422caa06b0bc)
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://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=62353048e2d4e398cfc22dbee3e1a7f6f535dcc1
git remote add linux-stable-rc https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git fetch --no-tags linux-stable-rc linux-5.4.y
git checkout 62353048e2d4e398cfc22dbee3e1a7f6f535dcc1
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=hexagon
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/staging/wilc1000/wilc_wfi_cfgoperations.c:61:42: warning: unused variable 'wowlan_support' [-Wunused-const-variable]
static const struct wiphy_wowlan_support wowlan_support = {
^
1 warning generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for FRAME_POINTER
Depends on DEBUG_KERNEL && (M68K || UML || SUPERH) || ARCH_WANT_FRAME_POINTERS
Selected by
- LOCKDEP && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT && !MIPS && !PPC && !ARM && !S390 && !MICROBLAZE && !ARC && !X86
vim +/wowlan_support +61 drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
15162fbc78a74a5 Arnd Bergmann 2015-11-16 60
73584a40d7484f1 Glen Lee 2016-01-25 @61 static const struct wiphy_wowlan_support wowlan_support = {
73584a40d7484f1 Glen Lee 2016-01-25 62 .flags = WIPHY_WOWLAN_ANY
73584a40d7484f1 Glen Lee 2016-01-25 63 };
73584a40d7484f1 Glen Lee 2016-01-25 64
:::::: The code at line 61 was first introduced by commit
:::::: 73584a40d7484f199a98893e97dcea8b2cbe4986 staging: wilc1000: add ops resuem/suspend/wakeup in cfg80211
:::::: TO: Glen Lee <glen.lee@atmel.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32169 bytes --]
reply other threads:[~2021-08-31 6:41 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=202108311442.hiXBftay-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
/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