From: kernel test robot <lkp@intel.com>
To: Shahar S Matityahu <shahar.s.matityahu@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Luca Coelho <luciano.coelho@intel.com>
Subject: drivers/net/wireless/intel/iwlwifi/mvm/scan.c:2094 iwl_mvm_scan_umac_v14() warn: inconsistent indenting
Date: Mon, 8 Feb 2021 07:09:49 +0800 [thread overview]
Message-ID: <202102080746.psQDG4eR-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 61556703b610a104de324e4f061dc6cf7b218b46
commit: 453f26822844bf08991616b9d5def122deba8514 iwlwifi: scan: support scan req cmd ver 14
date: 11 months ago
config: x86_64-randconfig-m001-20210208 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
New smatch warnings:
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:2094 iwl_mvm_scan_umac_v14() warn: inconsistent indenting
Old smatch warnings:
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:2027 iwl_mvm_scan_umac_v12() warn: inconsistent indenting
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:2060 iwl_mvm_scan_umac_v13() warn: inconsistent indenting
vim +2094 drivers/net/wireless/intel/iwlwifi/mvm/scan.c
2073
2074 static int iwl_mvm_scan_umac_v14(struct iwl_mvm *mvm, struct ieee80211_vif *vif,
2075 struct iwl_mvm_scan_params *params, int type,
2076 int uid)
2077 {
2078 struct iwl_scan_req_umac_v14 *cmd = mvm->scan_cmd;
2079 struct iwl_scan_req_params_v14 *scan_p = &cmd->scan_params;
2080 int ret;
2081 u16 gen_flags;
2082 u32 bitmap_ssid = 0;
2083
2084 mvm->scan_uid_status[uid] = type;
2085
2086 cmd->ooc_priority = cpu_to_le32(iwl_mvm_scan_umac_ooc_priority(params));
2087 cmd->uid = cpu_to_le32(uid);
2088
2089 gen_flags = iwl_mvm_scan_umac_flags_v2(mvm, params, vif, type);
2090 iwl_mvm_scan_umac_fill_general_p_v10(mvm, params, vif,
2091 &scan_p->general_params,
2092 gen_flags);
2093
> 2094 ret = iwl_mvm_fill_scan_sched_params(params,
2095 scan_p->periodic_params.schedule,
2096 &scan_p->periodic_params.delay);
2097 if (ret)
2098 return ret;
2099
2100 iwl_mvm_scan_umac_fill_probe_p_v4(params, &scan_p->probe_params,
2101 &bitmap_ssid);
2102 iwl_mvm_scan_umac_fill_ch_p_v6(mvm, params, vif,
2103 &scan_p->channel_params, bitmap_ssid);
2104
2105 return 0;
2106 }
2107
---
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: 38134 bytes --]
reply other threads:[~2021-02-07 23:11 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=202102080746.psQDG4eR-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=shahar.s.matityahu@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