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,
Kalle Valo <kvalo@codeaurora.org>,
Luca Coelho <luciano.coelho@intel.com>
Subject: drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1981 iwl_mvm_scan_umac_v12() warn: inconsistent indenting
Date: Fri, 12 Jun 2020 20:45:59 +0800 [thread overview]
Message-ID: <202006122056.oLjJbjmx%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2057 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b791d1bdf9212d944d749a5c7ff6febdba241771
commit: 5167ff45a503ee49ae314c0cff410efa1eb9a1b8 iwlwifi: scan: support scan req cmd ver 12
date: 7 months ago
config: powerpc64-randconfig-m031-20200612 (attached as .config)
compiler: powerpc64le-linux-gcc (GCC) 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:1981 iwl_mvm_scan_umac_v12() warn: inconsistent indenting
Old smatch warnings:
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1949 iwl_mvm_scan_umac_v11() warn: inconsistent indenting
vim +1981 drivers/net/wireless/intel/iwlwifi/mvm/scan.c
1961
1962 static int iwl_mvm_scan_umac_v12(struct iwl_mvm *mvm, struct ieee80211_vif *vif,
1963 struct iwl_mvm_scan_params *params, int type,
1964 int uid)
1965 {
1966 struct iwl_scan_req_umac_v12 *cmd = mvm->scan_cmd;
1967 struct iwl_scan_req_params_v12 *scan_p = &cmd->scan_params;
1968 int ret;
1969 u16 gen_flags;
1970
1971 mvm->scan_uid_status[uid] = type;
1972
1973 cmd->ooc_priority = cpu_to_le32(iwl_mvm_scan_umac_ooc_priority(params));
1974 cmd->uid = cpu_to_le32(uid);
1975
1976 gen_flags = iwl_mvm_scan_umac_flags_v2(mvm, params, vif, type);
1977 iwl_mvm_scan_umac_fill_general_p_v10(mvm, params, vif,
1978 &scan_p->general_params,
1979 gen_flags);
1980
> 1981 ret = iwl_mvm_fill_scan_sched_params(params,
1982 scan_p->periodic_params.schedule,
1983 &scan_p->periodic_params.delay);
1984 if (ret)
1985 return ret;
1986
1987 iwl_mvm_scan_umac_fill_probe_p_v3(params, &scan_p->probe_params);
1988 iwl_mvm_scan_umac_fill_ch_p_v4(mvm, params, vif,
1989 &scan_p->channel_params);
1990
1991 return 0;
1992 }
1993
---
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: 35234 bytes --]
reply other threads:[~2020-06-12 12:55 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=202006122056.oLjJbjmx%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvalo@codeaurora.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
all inboxes | Powered by JetHome®