From: kernel test robot <lkp@intel.com>
To: Mohammed Anees <pvmohammedanees2003@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Ping-Ke Shih <pkshih@realtek.com>,
Kalle Valo <kvalo@kernel.org>,
Mohammed Anees <pvmohammedanees2003@gmail.com>
Subject: Re: [PATCH] wifi: rtw88: Refactor looping in rtw_phy_store_tx_power_by_rate
Date: Thu, 17 Oct 2024 11:19:30 +0800 [thread overview]
Message-ID: <202410171143.OnFlgIwK-lkp@intel.com> (raw)
In-Reply-To: <20241016060605.11359-1-pvmohammedanees2003@gmail.com>
Hi Mohammed,
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.12-rc3 next-20241016]
[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/Mohammed-Anees/wifi-rtw88-Refactor-looping-in-rtw_phy_store_tx_power_by_rate/20241016-140811
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link: https://lore.kernel.org/r/20241016060605.11359-1-pvmohammedanees2003%40gmail.com
patch subject: [PATCH] wifi: rtw88: Refactor looping in rtw_phy_store_tx_power_by_rate
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20241017/202410171143.OnFlgIwK-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241017/202410171143.OnFlgIwK-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/202410171143.OnFlgIwK-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/wireless/realtek/rtw88/phy.c: In function 'rtw_phy_store_tx_power_by_rate':
>> drivers/net/wireless/realtek/rtw88/phy.c:1468:48: error: 'PHY_BANK_2G' undeclared (first use in this function); did you mean 'PHY_BAND_2G'?
1468 | s8 (*tx_pwr_by_rate_offset) = (band == PHY_BANK_2G)
| ^~~~~~~~~~~
| PHY_BAND_2G
drivers/net/wireless/realtek/rtw88/phy.c:1468:48: note: each undeclared identifier is reported only once for each function it appears in
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [m]:
- RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m]
vim +1468 drivers/net/wireless/realtek/rtw88/phy.c
1447
1448 static void rtw_phy_store_tx_power_by_rate(struct rtw_dev *rtwdev,
1449 u32 band, u32 rfpath, u32 txnum,
1450 u32 regaddr, u32 bitmask, u32 data)
1451 {
1452 struct rtw_hal *hal = &rtwdev->hal;
1453 u8 rate_num = 0;
1454 u8 rate;
1455 u8 rates[RTW_RF_PATH_MAX] = {0};
1456 s8 offset;
1457 s8 pwr_by_rate[RTW_RF_PATH_MAX] = {0};
1458 int i;
1459
1460 rtw_phy_get_rate_values_of_txpwr_by_rate(rtwdev, regaddr, bitmask, data,
1461 rates, pwr_by_rate, &rate_num);
1462
1463 if (WARN_ON(rfpath >= RTW_RF_PATH_MAX ||
1464 (band != PHY_BAND_2G && band != PHY_BAND_5G) ||
1465 rate_num > RTW_RF_PATH_MAX))
1466 return;
1467
> 1468 s8 (*tx_pwr_by_rate_offset) = (band == PHY_BANK_2G)
1469 ? hal->tx_pwr_by_rate_offset_2g[rfpath]
1470 : hal->tx_pwr_by_rate_offset_5g[rfpath];
1471
1472 for (i = 0; i < rate_num; i++) {
1473 offset = pwr_by_rate[i];
1474 rate = rates[i];
1475 tx_pwr_by_rate_offset[rate] = offset;
1476 }
1477 }
1478
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-17 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 6:06 Mohammed Anees
2024-10-17 1:21 ` Ping-Ke Shih
2024-10-17 6:56 ` Mohammed Anees
2024-10-17 7:06 ` Ping-Ke Shih
2024-10-17 7:12 ` Mohammed Anees
2024-10-17 3:19 ` kernel test robot [this message]
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=202410171143.OnFlgIwK-lkp@intel.com \
--to=lkp@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pkshih@realtek.com \
--cc=pvmohammedanees2003@gmail.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®