From: kernel test robot <lkp@intel.com>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Kalle Valo <kvalo@kernel.org>,
Luca Coelho <luciano.coelho@intel.com>
Subject: [linux-next:master 3193/5417] drivers/net/wireless/intel/iwlwifi/mvm/mvm.h:2228:24: error: implicit declaration of function 'rfkill_soft_blocked'
Date: Sun, 13 Feb 2022 04:40:04 +0800 [thread overview]
Message-ID: <202202130409.S6QHJomb-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6d9bd4ad4ca08b1114e814c2c42383b8b13be631
commit: 7cf800f46e07e6b75a43036c4389d6ca717fd017 [3193/5417] iwlwifi: mvm: don't feed the hardware RFKILL into iwlmei
config: riscv-randconfig-r042-20220213 (https://download.01.org/0day-ci/archive/20220213/202202130409.S6QHJomb-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c7eb84634519e6497be42f5fe323f9a04ed67127)
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 riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=7cf800f46e07e6b75a43036c4389d6ca717fd017
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 7cf800f46e07e6b75a43036c4389d6ca717fd017
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/net/wireless/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/net/wireless/intel/iwlwifi/mvm/fw.c:19:
>> drivers/net/wireless/intel/iwlwifi/mvm/mvm.h:2228:24: error: implicit declaration of function 'rfkill_soft_blocked' [-Werror,-Wimplicit-function-declaration]
mvm->hw_registered ? rfkill_soft_blocked(mvm->hw->wiphy->rfkill) : false;
^
drivers/net/wireless/intel/iwlwifi/mvm/mvm.h:2228:24: note: did you mean 'rfkill_blocked'?
include/linux/rfkill.h:306:20: note: 'rfkill_blocked' declared here
static inline bool rfkill_blocked(struct rfkill *rfkill)
^
1 error generated.
--
In file included from drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c:9:
>> drivers/net/wireless/intel/iwlwifi/mvm/mvm.h:2228:24: error: implicit declaration of function 'rfkill_soft_blocked' [-Werror,-Wimplicit-function-declaration]
mvm->hw_registered ? rfkill_soft_blocked(mvm->hw->wiphy->rfkill) : false;
^
drivers/net/wireless/intel/iwlwifi/mvm/mvm.h:2228:24: note: did you mean 'rfkill_blocked'?
include/linux/rfkill.h:306:20: note: 'rfkill_blocked' declared here
static inline bool rfkill_blocked(struct rfkill *rfkill)
^
drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c:1109:47: warning: format specifies type 'unsigned char' but the argument has type 's16' (aka 'short') [-Wformat]
IWL_DEBUG_INFO(mvm, "\tburst index: %hhu\n", res->ftm.burst_index);
~~~~ ^~~~~~~~~~~~~~~~~~~~
%hd
drivers/net/wireless/intel/iwlwifi/mvm/../iwl-debug.h:175:68: note: expanded from macro 'IWL_DEBUG_INFO'
#define IWL_DEBUG_INFO(p, f, a...) IWL_DEBUG(p, IWL_DL_INFO, f, ## a)
~ ^
drivers/net/wireless/intel/iwlwifi/mvm/../iwl-debug.h:94:49: note: expanded from macro 'IWL_DEBUG'
__IWL_DEBUG_DEV((m)->dev, level, false, fmt, ##args)
~~~ ^~~~
drivers/net/wireless/intel/iwlwifi/mvm/../iwl-debug.h:91:49: note: expanded from macro '__IWL_DEBUG_DEV'
__iwl_dbg(dev, level, limit, __func__, fmt, ##args); \
~~~ ^~~~
drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c:1112:47: warning: format specifies type 'unsigned char' but the argument has type 's32' (aka 'int') [-Wformat]
IWL_DEBUG_INFO(mvm, "\trssi spread: %hhu\n", res->ftm.rssi_spread);
~~~~ ^~~~~~~~~~~~~~~~~~~~
%d
drivers/net/wireless/intel/iwlwifi/mvm/../iwl-debug.h:175:68: note: expanded from macro 'IWL_DEBUG_INFO'
#define IWL_DEBUG_INFO(p, f, a...) IWL_DEBUG(p, IWL_DL_INFO, f, ## a)
~ ^
drivers/net/wireless/intel/iwlwifi/mvm/../iwl-debug.h:94:49: note: expanded from macro 'IWL_DEBUG'
__IWL_DEBUG_DEV((m)->dev, level, false, fmt, ##args)
~~~ ^~~~
drivers/net/wireless/intel/iwlwifi/mvm/../iwl-debug.h:91:49: note: expanded from macro '__IWL_DEBUG_DEV'
__iwl_dbg(dev, level, limit, __func__, fmt, ##args); \
~~~ ^~~~
2 warnings and 1 error generated.
vim +/rfkill_soft_blocked +2228 drivers/net/wireless/intel/iwlwifi/mvm/mvm.h
2224
2225 static inline void iwl_mvm_mei_set_sw_rfkill_state(struct iwl_mvm *mvm)
2226 {
2227 bool sw_rfkill =
> 2228 mvm->hw_registered ? rfkill_soft_blocked(mvm->hw->wiphy->rfkill) : false;
2229
2230 if (mvm->mei_registered)
2231 iwl_mei_set_rfkill_state(iwl_mvm_is_radio_killed(mvm),
2232 sw_rfkill);
2233 }
2234
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-12 20:40 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=202202130409.S6QHJomb-lkp@intel.com \
--to=lkp@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvalo@kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=luciano.coelho@intel.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