From: kernel test robot <lkp@intel.com>
To: Junxian Huang <huangjunxian6@hisilicon.com>,
jgg@nvidia.com, leon@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-rdma@vger.kernel.org,
linuxarm@huawei.com, linux-kernel@vger.kernel.org,
huangjunxian6@hisilicon.com
Subject: Re: [PATCH v2 for-rc 3/3] RDMA/hns: Add check and adjust for function resource values
Date: Wed, 19 Jul 2023 01:02:58 +0800 [thread overview]
Message-ID: <202307190042.hWzQQIOk-lkp@intel.com> (raw)
In-Reply-To: <20230717060340.453850-4-huangjunxian6@hisilicon.com>
Hi Junxian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rdma/for-next]
[also build test WARNING on linus/master v6.5-rc2 next-20230718]
[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/Junxian-Huang/RDMA-hns-support-get-xrcd-num-from-firmware/20230718-171525
base: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
patch link: https://lore.kernel.org/r/20230717060340.453850-4-huangjunxian6%40hisilicon.com
patch subject: [PATCH v2 for-rc 3/3] RDMA/hns: Add check and adjust for function resource values
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20230719/202307190042.hWzQQIOk-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230719/202307190042.hWzQQIOk-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/202307190042.hWzQQIOk-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/infiniband/hw/hns/hns_roce_hw_v2.c: In function 'adjust_res_caps':
>> drivers/infiniband/hw/hns/hns_roce_hw_v2.c:1709:53: warning: passing argument 2 of 'check_res_is_supported' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
1709 | if (!check_res_is_supported(hr_dev, &bt_num_table[i]))
| ^~~~~~~~~~~~~~~~
drivers/infiniband/hw/hns/hns_roce_hw_v2.c:1673:60: note: expected 'struct hns_roce_bt_num *' but argument is of type 'const struct hns_roce_bt_num *'
1673 | struct hns_roce_bt_num *bt_num_entry)
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
vim +1709 drivers/infiniband/hw/hns/hns_roce_hw_v2.c
1699
1700 static u16 adjust_res_caps(struct hns_roce_dev *hr_dev)
1701 {
1702 struct hns_roce_caps *caps = &hr_dev->caps;
1703 u16 invalid_flag = 0;
1704 u32 min, max;
1705 u32 *res;
1706 int i;
1707
1708 for (i = 0; i < ARRAY_SIZE(bt_num_table); i++) {
> 1709 if (!check_res_is_supported(hr_dev, &bt_num_table[i]))
1710 continue;
1711
1712 res = (u32 *)((void *)caps + bt_num_table[i].res_offset);
1713 min = bt_num_table[i].min;
1714 max = bt_num_table[i].max;
1715 if (*res < min || *res > max) {
1716 *res = *res < min ? min : max;
1717 invalid_flag |= 1 << bt_num_table[i].invalid_flag;
1718 }
1719 }
1720
1721 adjust_eqc_bt_num(caps, &invalid_flag);
1722
1723 return invalid_flag;
1724 }
1725
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-07-18 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 6:03 [PATCH v2 for-rc 0/3] RDMA/hns: Improvements for function resource configuration Junxian Huang
2023-07-17 6:03 ` [PATCH v2 for-rc 1/3] RDMA/hns: support get xrcd num from firmware Junxian Huang
2023-07-17 6:03 ` [PATCH v2 for-rc 2/3] RDMA/hns: Remove VF extend configuration Junxian Huang
2023-07-17 6:03 ` [PATCH v2 for-rc 3/3] RDMA/hns: Add check and adjust for function resource values Junxian Huang
2023-07-17 8:10 ` Leon Romanovsky
2023-07-18 17:02 ` 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=202307190042.hWzQQIOk-lkp@intel.com \
--to=lkp@intel.com \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.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
Powered by JetHome