From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 6/9] RDMA/rxe: Implement flush execution in responder side
Date: Wed, 26 Jan 2022 04:18:55 +0800 [thread overview]
Message-ID: <202201260421.itl2Uin2-lkp@intel.com> (raw)
In-Reply-To: <20220125085041.49175-7-lizhijian@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 2268 bytes --]
Hi Li,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on rdma/for-next]
[also build test WARNING on v5.17-rc1 next-20220125]
[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/Li-Zhijian/RDMA-rxe-Add-RDMA-FLUSH-operation/20220125-165822
base: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
config: x86_64-randconfig-s022-20220124 (https://download.01.org/0day-ci/archive/20220126/202201260421.itl2Uin2-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/9b2af9620176faaaeb82f157062b73ba6b0c791b
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Li-Zhijian/RDMA-rxe-Add-RDMA-FLUSH-operation/20220125-165822
git checkout 9b2af9620176faaaeb82f157062b73ba6b0c791b
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/infiniband/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/infiniband/sw/rxe/rxe_resp.c: note: in included file (through drivers/infiniband/sw/rxe/rxe.h):
>> drivers/infiniband/sw/rxe/rxe_hdr.h:636:20: sparse: sparse: cast to restricted __be32
drivers/infiniband/sw/rxe/rxe_hdr.h:644:20: sparse: sparse: cast to restricted __be32
>> drivers/infiniband/sw/rxe/rxe_hdr.h:636:20: sparse: sparse: cast to restricted __be32
vim +636 drivers/infiniband/sw/rxe/rxe_hdr.h
632
633 static inline u32 __feth_plt(void *arg)
634 {
635 u32 *fethp = arg;
> 636 u32 feth = be32_to_cpu(*fethp);
637
638 return (feth & FETH_PLT_MASK) >> FETH_PLT_SHIFT;
639 }
640
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2022-01-25 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 8:50 [RFC PATCH v2 0/9] RDMA/rxe: Add RDMA FLUSH operation Li Zhijian
2022-01-25 8:50 ` [RFC PATCH v2 1/9] RDMA: mr: Introduce is_pmem Li Zhijian
2022-01-25 8:50 ` [RFC PATCH v2 2/9] RDMA: Allow registering MR with flush access flags Li Zhijian
2022-01-25 8:50 ` [RFC PATCH v2 3/9] RDMA/rxe: Allow registering persistent flag for pmem MR only Li Zhijian
2022-01-25 8:50 ` [RFC PATCH v2 4/9] RDMA/rxe: Implement RC RDMA FLUSH service in requester side Li Zhijian
2022-01-25 19:17 ` kernel test robot
2022-01-25 8:50 ` [RFC PATCH v2 5/9] RDMA/rxe: Set BTH's SE to zero for FLUSH packet Li Zhijian
2022-01-25 8:50 ` [RFC PATCH v2 6/9] RDMA/rxe: Implement flush execution in responder side Li Zhijian
2022-01-25 20:18 ` kernel test robot [this message]
2022-01-25 8:50 ` [RFC PATCH v2 7/9] RDMA/rxe: Implement flush completion Li Zhijian
2022-01-25 8:50 ` [RFC PATCH v2 8/9] RDMA/rxe: Enable RDMA FLUSH capability for rxe device Li Zhijian
2022-01-25 8:50 ` [RFC PATCH v2 9/9] RDMA/rxe: Add RD FLUSH service support Li Zhijian
2022-01-25 8:57 ` [RFC PATCH v2 0/9] RDMA/rxe: Add RDMA FLUSH operation Zhu Yanjun
2022-01-25 10:32 ` lizhijian
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=202201260421.itl2Uin2-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.