public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>,
	johannes@sipsolutions.net
Cc: oe-kbuild-all@lists.linux.dev, linux-wireless@vger.kernel.org,
	Andrei Otcheretianski <andrei.otcheretianski@intel.com>,
	Gregory Greenman <gregory.greenman@intel.com>
Subject: Re: [PATCH 02/14] wifi: iwlwifi: mvm: Allow DFS concurrent operation
Date: Thu, 21 Dec 2023 04:02:31 +0800	[thread overview]
Message-ID: <202312210343.J7eedmDf-lkp@intel.com> (raw)
In-Reply-To: <20231219215605.dc39b33bf507.I04dfda24d73091fb75701279d10ac400314de488@changeid>

Hi Miri,

kernel test robot noticed the following build errors:

[auto build test ERROR on wireless-next/main]
[also build test ERROR on wireless/main linus/master v6.7-rc6 next-20231220]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Miri-Korenblit/iwlwifi-mvm-set-siso-mimo-chains-to-1-in-FW-SMPS-request/20231220-040247
base:   https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link:    https://lore.kernel.org/r/20231219215605.dc39b33bf507.I04dfda24d73091fb75701279d10ac400314de488%40changeid
patch subject: [PATCH 02/14] wifi: iwlwifi: mvm: Allow DFS concurrent operation
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20231221/202312210343.J7eedmDf-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231221/202312210343.J7eedmDf-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/oe-kbuild-all/202312210343.J7eedmDf-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c: In function 'iwl_nvm_get_regdom_bw_flags':
>> drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c:1616:34: error: 'NL80211_RRF_DFS_CONCURRENT' undeclared (first use in this function); did you mean 'NL80211_RRF_IR_CONCURRENT'?
    1616 |                         flags |= NL80211_RRF_DFS_CONCURRENT;
         |                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~
         |                                  NL80211_RRF_IR_CONCURRENT
   drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c:1616:34: note: each undeclared identifier is reported only once for each function it appears in
--
   drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c: In function 'iwl_mvm_mac_setup_register':
>> drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:522:39: error: 'NL80211_EXT_FEATURE_DFS_CONCURRENT' undeclared (first use in this function); did you mean 'NL80211_EXT_FEATURE_BSS_COLOR'?
     522 |                                       NL80211_EXT_FEATURE_DFS_CONCURRENT);
         |                                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         |                                       NL80211_EXT_FEATURE_BSS_COLOR
   drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:522:39: note: each undeclared identifier is reported only once for each function it appears in


vim +1616 drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c

  1574	
  1575	static u32 iwl_nvm_get_regdom_bw_flags(const u16 *nvm_chan,
  1576					       int ch_idx, u16 nvm_flags,
  1577					       struct iwl_reg_capa reg_capa,
  1578					       const struct iwl_cfg *cfg)
  1579	{
  1580		u32 flags = NL80211_RRF_NO_HT40;
  1581	
  1582		if (ch_idx < NUM_2GHZ_CHANNELS &&
  1583		    (nvm_flags & NVM_CHANNEL_40MHZ)) {
  1584			if (nvm_chan[ch_idx] <= LAST_2GHZ_HT_PLUS)
  1585				flags &= ~NL80211_RRF_NO_HT40PLUS;
  1586			if (nvm_chan[ch_idx] >= FIRST_2GHZ_HT_MINUS)
  1587				flags &= ~NL80211_RRF_NO_HT40MINUS;
  1588		} else if (nvm_flags & NVM_CHANNEL_40MHZ) {
  1589			if ((ch_idx - NUM_2GHZ_CHANNELS) % 2 == 0)
  1590				flags &= ~NL80211_RRF_NO_HT40PLUS;
  1591			else
  1592				flags &= ~NL80211_RRF_NO_HT40MINUS;
  1593		}
  1594	
  1595		if (!(nvm_flags & NVM_CHANNEL_80MHZ))
  1596			flags |= NL80211_RRF_NO_80MHZ;
  1597		if (!(nvm_flags & NVM_CHANNEL_160MHZ))
  1598			flags |= NL80211_RRF_NO_160MHZ;
  1599	
  1600		if (!(nvm_flags & NVM_CHANNEL_ACTIVE))
  1601			flags |= NL80211_RRF_NO_IR;
  1602	
  1603		if (nvm_flags & NVM_CHANNEL_RADAR)
  1604			flags |= NL80211_RRF_DFS;
  1605	
  1606		if (nvm_flags & NVM_CHANNEL_INDOOR_ONLY)
  1607			flags |= NL80211_RRF_NO_OUTDOOR;
  1608	
  1609		/* Set the GO concurrent flag only in case that NO_IR is set.
  1610		 * Otherwise it is meaningless
  1611		 */
  1612		if ((nvm_flags & NVM_CHANNEL_GO_CONCURRENT)) {
  1613			if (flags & NL80211_RRF_NO_IR)
  1614				flags |= NL80211_RRF_GO_CONCURRENT;
  1615			if (flags & NL80211_RRF_DFS)
> 1616				flags |= NL80211_RRF_DFS_CONCURRENT;
  1617		}
  1618		/*
  1619		 * reg_capa is per regulatory domain so apply it for every channel
  1620		 */
  1621		if (ch_idx >= NUM_2GHZ_CHANNELS) {
  1622			if (!reg_capa.allow_40mhz)
  1623				flags |= NL80211_RRF_NO_HT40;
  1624	
  1625			if (!reg_capa.allow_80mhz)
  1626				flags |= NL80211_RRF_NO_80MHZ;
  1627	
  1628			if (!reg_capa.allow_160mhz)
  1629				flags |= NL80211_RRF_NO_160MHZ;
  1630	
  1631			if (!reg_capa.allow_320mhz)
  1632				flags |= NL80211_RRF_NO_320MHZ;
  1633		}
  1634	
  1635		if (reg_capa.disable_11ax)
  1636			flags |= NL80211_RRF_NO_HE;
  1637	
  1638		if (reg_capa.disable_11be)
  1639			flags |= NL80211_RRF_NO_EHT;
  1640	
  1641		return flags;
  1642	}
  1643	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2023-12-20 20:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 19:58 [PATCH 00/14] wifi: iwlwifi: updates - 2023-12-06 Miri Korenblit
2023-12-19 19:58 ` [PATCH 01/14] iwlwifi: mvm: set siso/mimo chains to 1 in FW SMPS request Miri Korenblit
2023-12-19 19:58 ` [PATCH 02/14] wifi: iwlwifi: mvm: Allow DFS concurrent operation Miri Korenblit
2023-12-20 19:42   ` kernel test robot
2023-12-20 20:02   ` kernel test robot [this message]
2023-12-19 19:58 ` [PATCH 03/14] wifi: iwlwifi: Don't mark DFS channels as NO-IR Miri Korenblit
2023-12-19 19:58 ` [PATCH 04/14] wifi: iwlwifi: mvm: send TX path flush in rfkill Miri Korenblit
2023-12-19 19:58 ` [PATCH 05/14] wifi: iwlwifi: mvm: d3: avoid intermediate/early mutex unlock Miri Korenblit
2023-12-19 19:58 ` [PATCH 06/14] wifi: iwlwifi: mvm: Do not warn if valid link pair was not found Miri Korenblit
2023-12-19 19:58 ` [PATCH 07/14] wifi: iwlwifi: fix out of bound copy_from_user Miri Korenblit
2023-12-19 19:58 ` [PATCH 08/14] wifi: iwlwifi: assign phy_ctxt before eSR activation Miri Korenblit
2023-12-19 19:58 ` [PATCH 09/14] wifi: iwlwifi: cleanup BT Shared Single Antenna code Miri Korenblit
2023-12-19 19:58 ` [PATCH 10/14] wifi: iwlwifi: Add rf_mapping of new wifi7 devices Miri Korenblit
2023-12-19 19:58 ` [PATCH 11/14] wifi: iwlwifi: mvm: add US/Canada MCC to API Miri Korenblit
2023-12-19 19:59 ` [PATCH 12/14] wifi: iwlwifi: mvm: disallow puncturing in US/Canada Miri Korenblit
2023-12-19 19:59 ` [PATCH 13/14] wifi: iwlwifi: mvm: use the new command to clear the internal buffer Miri Korenblit
2023-12-19 19:59 ` [PATCH 14/14] wifi: iwlwifi: replace ENOTSUPP with EOPNOTSUPP Miri Korenblit
  -- strict thread matches above, loose matches on Subject: below --
2023-12-20 13:29 [PATCH 00/14] wifi: iwlwifi: updates - 2023-12-19 Miri Korenblit
2023-12-20 13:29 ` [PATCH 02/14] wifi: iwlwifi: mvm: Allow DFS concurrent operation Miri Korenblit

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=202312210343.J7eedmDf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrei.otcheretianski@intel.com \
    --cc=gregory.greenman@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.com \
    --cc=oe-kbuild-all@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