From: kernel test robot <lkp@intel.com>
To: Bob Pearson <rpearsonhpe@gmail.com>,
jgg@nvidia.com, zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Cc: kbuild-all@lists.01.org, Bob Pearson <rpearson@hpe.com>
Subject: Re: [PATCH for-next] RDMA/rxe: fix regression caused by recent patch
Date: Fri, 30 Oct 2020 10:39:15 +0800 [thread overview]
Message-ID: <202010301021.ONKtCFmX-lkp@intel.com> (raw)
In-Reply-To: <20201029212545.6616-1-rpearson@hpe.com>
[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]
Hi Bob,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on rdma/for-next]
[also build test WARNING on v5.10-rc1 next-20201029]
[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/Bob-Pearson/RDMA-rxe-fix-regression-caused-by-recent-patch/20201030-052848
base: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-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/880fe509bd2bdc73c885fd887cb3935000855d49
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Bob-Pearson/RDMA-rxe-fix-regression-caused-by-recent-patch/20201030-052848
git checkout 880fe509bd2bdc73c885fd887cb3935000855d49
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
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/sw/rxe/rxe_verbs.c: In function 'rxe_register_device':
>> drivers/infiniband/sw/rxe/rxe_verbs.c:1143:20: warning: assignment to 'u64 *' {aka 'long long unsigned int *'} from 'long long unsigned int' makes pointer from integer without a cast [-Wint-conversion]
1143 | dev->dev.dma_mask = DMA_BIT_MASK(64);
| ^
vim +1143 drivers/infiniband/sw/rxe/rxe_verbs.c
1125
1126 int rxe_register_device(struct rxe_dev *rxe, const char *ibdev_name)
1127 {
1128 int err;
1129 struct ib_device *dev = &rxe->ib_dev;
1130 struct crypto_shash *tfm;
1131
1132 strlcpy(dev->node_desc, "rxe", sizeof(dev->node_desc));
1133
1134 dev->node_type = RDMA_NODE_IB_CA;
1135 dev->phys_port_cnt = 1;
1136 dev->num_comp_vectors = num_possible_cpus();
1137
1138 /* rdma_rxe never does real DMA but does rely on
1139 * pinning user memory in MRs to avoid page faults
1140 * in responder and completer tasklets
1141 */
1142 dev->dev.parent = rxe_dma_device(rxe);
> 1143 dev->dev.dma_mask = DMA_BIT_MASK(64);
---
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: 71486 bytes --]
next prev parent reply other threads:[~2020-10-30 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 21:25 [PATCH for-next] RDMA/rxe: fix regression caused by recent patch Bob Pearson
2020-10-30 2:39 ` kernel test robot [this message]
2020-10-30 2:54 ` Zhu Yanjun
2020-10-30 5:46 ` Bob Pearson
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=202010301021.ONKtCFmX-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearson@hpe.com \
--cc=rpearsonhpe@gmail.com \
--cc=zyjzyj2000@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