From: kernel test robot <lkp@intel.com>
To: Weihang Li <liweihang@huawei.com>, dledford@redhat.com, jgg@nvidia.com
Cc: kbuild-all@lists.01.org, leon@kernel.org,
linux-rdma@vger.kernel.org, linuxarm@openeuler.org
Subject: Re: [PATCH for-next 2/3] RDMA/hns: Optimize the MR registration process
Date: Fri, 22 Jan 2021 01:51:25 +0800 [thread overview]
Message-ID: <202101220137.7nVVZStH-lkp@intel.com> (raw)
In-Reply-To: <1611236882-41498-3-git-send-email-liweihang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]
Hi Weihang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on rdma/for-next]
[also build test WARNING on v5.11-rc4 next-20210121]
[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]
url: https://github.com/0day-ci/linux/commits/Weihang-Li/RDMA-hns-Refactor-codes-about-memory/20210121-215817
base: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
config: sparc-allyesconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/9ff47c3f8e6b778282c3bc9d4fb65ce835bdd83c
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Weihang-Li/RDMA-hns-Refactor-codes-about-memory/20210121-215817
git checkout 9ff47c3f8e6b778282c3bc9d4fb65ce835bdd83c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sparc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/infiniband/hw/hns/hns_roce_mr.c:140:6: warning: no previous prototype for 'hns_roce_mr_free' [-Wmissing-prototypes]
140 | void hns_roce_mr_free(struct hns_roce_dev *hr_dev, struct hns_roce_mr *mr)
| ^~~~~~~~~~~~~~~~
vim +/hns_roce_mr_free +140 drivers/infiniband/hw/hns/hns_roce_mr.c
139
> 140 void hns_roce_mr_free(struct hns_roce_dev *hr_dev, struct hns_roce_mr *mr)
141 {
142 struct ib_device *ibdev = &hr_dev->ib_dev;
143 int ret;
144
145 if (mr->enabled) {
146 ret = hns_roce_hw_destroy_mpt(hr_dev, NULL,
147 key_to_hw_index(mr->key) &
148 (hr_dev->caps.num_mtpts - 1));
149 if (ret)
150 ibdev_warn(ibdev, "failed to destroy mpt, ret = %d.\n",
151 ret);
152 }
153
154 free_mr_pbl(hr_dev, mr);
155 free_mr_key(hr_dev, mr);
156 }
157
---
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: 68790 bytes --]
next prev parent reply other threads:[~2021-01-21 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 13:47 [PATCH for-next 0/3] RDMA/hns: Refactor codes about memory Weihang Li
2021-01-21 13:48 ` [PATCH for-next 1/3] RDMA/hns: Refactor the MTR creation flow Weihang Li
2021-01-21 13:48 ` [PATCH for-next 2/3] RDMA/hns: Optimize the MR registration process Weihang Li
2021-01-21 17:51 ` kernel test robot [this message]
2021-01-21 13:48 ` [PATCH for-next 3/3] RDMA/hns: Use new interface to set MPT related fields Weihang Li
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=202101220137.7nVVZStH-lkp@intel.com \
--to=lkp@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=liweihang@huawei.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