From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: Re: [PATCH 14/14] RDMA/ionic: Add Makefile/Kconfig to kernel build environment
Date: Wed, 7 May 2025 21:08:15 +0800 [thread overview]
Message-ID: <202505072012.NkkKd0ba-lkp@intel.com> (raw)
In-Reply-To: <20250423102913.438027-15-abhijit.gangurde@amd.com>
References: <20250423102913.438027-15-abhijit.gangurde@amd.com>
TO: Abhijit Gangurde <abhijit.gangurde@amd.com>
TO: shannon.nelson@amd.com
TO: brett.creeley@amd.com
TO: davem@davemloft.net
TO: edumazet@google.com
TO: kuba@kernel.org
TO: pabeni@redhat.com
TO: corbet@lwn.net
TO: jgg@ziepe.ca
TO: leon@kernel.org
TO: andrew+netdev@lunn.ch
CC: allen.hubbe@amd.com
CC: nikhil.agarwal@amd.com
CC: linux-rdma@vger.kernel.org
CC: netdev@vger.kernel.org
CC: linux-doc@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: Abhijit Gangurde <abhijit.gangurde@amd.com>
Hi Abhijit,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
[also build test WARNING on net/main linus/master v6.15-rc5 next-20250507]
[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/Abhijit-Gangurde/net-ionic-Rename-neqs_per_lif-to-reflect-rdma-capability/20250423-185723
base: net-next/main
patch link: https://lore.kernel.org/r/20250423102913.438027-15-abhijit.gangurde%40amd.com
patch subject: [PATCH 14/14] RDMA/ionic: Add Makefile/Kconfig to kernel build environment
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20250507/202505072012.NkkKd0ba-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250507/202505072012.NkkKd0ba-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/202505072012.NkkKd0ba-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/infiniband/hw/ionic/ionic_datapath.c:898:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
898 | wqe->base.op = IONIC_OP(dev->rdma_version, SEND);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:901:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
901 | wqe->base.op = IONIC_OP(dev->rdma_version, SEND_IMM);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:905:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
905 | wqe->base.op = IONIC_OP(dev->rdma_version, SEND_INV);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:942:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
942 | wqe->base.op = IONIC_OP(dev->rdma_version, SEND);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:945:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
945 | wqe->base.op = IONIC_OP(dev->rdma_version, SEND_IMM);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:974:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
974 | wqe->base.op = IONIC_OP(dev->rdma_version, RDMA_READ);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:979:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
979 | wqe->base.op = IONIC_OP(dev->rdma_version, RDMA_WRITE);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:982:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
982 | wqe->base.op = IONIC_OP(dev->rdma_version, RDMA_WRITE_IMM);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:1019:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
1019 | wqe->base.op = IONIC_OP(dev->rdma_version, ATOMIC_CS);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:1027:18: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
1027 | wqe->base.op = IONIC_OP(dev->rdma_version, ATOMIC_FA);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:1062:17: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
1062 | wqe->base.op = IONIC_OP(dev->rdma_version, LOCAL_INV);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:1097:17: warning: conditional expression between different enumeration types ('enum ionic_v1_op' and 'enum ionic_v2_op') [-Wenum-compare-conditional]
1097 | wqe->base.op = IONIC_OP(dev->rdma_version, REG_MR);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/ionic/ionic_datapath.c:13:17: note: expanded from macro 'IONIC_OP'
13 | ((version) < 2 ? IONIC_V1_OP_##opname : IONIC_V2_OP_##opname)
| ^ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
12 warnings generated.
vim +898 drivers/infiniband/hw/ionic/ionic_datapath.c
0c894fc5e53316 Abhijit Gangurde 2025-04-23 881
0c894fc5e53316 Abhijit Gangurde 2025-04-23 882 static int ionic_prep_send(struct ionic_qp *qp,
0c894fc5e53316 Abhijit Gangurde 2025-04-23 883 const struct ib_send_wr *wr)
0c894fc5e53316 Abhijit Gangurde 2025-04-23 884 {
0c894fc5e53316 Abhijit Gangurde 2025-04-23 885 struct ionic_ibdev *dev = to_ionic_ibdev(qp->ibqp.device);
0c894fc5e53316 Abhijit Gangurde 2025-04-23 886 struct ionic_sq_meta *meta;
0c894fc5e53316 Abhijit Gangurde 2025-04-23 887 struct ionic_v1_wqe *wqe;
0c894fc5e53316 Abhijit Gangurde 2025-04-23 888
0c894fc5e53316 Abhijit Gangurde 2025-04-23 889 meta = &qp->sq_meta[qp->sq.prod];
0c894fc5e53316 Abhijit Gangurde 2025-04-23 890 wqe = ionic_queue_at_prod(&qp->sq);
0c894fc5e53316 Abhijit Gangurde 2025-04-23 891
0c894fc5e53316 Abhijit Gangurde 2025-04-23 892 ionic_prep_sq_wqe(qp, wqe);
0c894fc5e53316 Abhijit Gangurde 2025-04-23 893
0c894fc5e53316 Abhijit Gangurde 2025-04-23 894 meta->ibop = IB_WC_SEND;
0c894fc5e53316 Abhijit Gangurde 2025-04-23 895
0c894fc5e53316 Abhijit Gangurde 2025-04-23 896 switch (wr->opcode) {
0c894fc5e53316 Abhijit Gangurde 2025-04-23 897 case IB_WR_SEND:
0c894fc5e53316 Abhijit Gangurde 2025-04-23 @898 wqe->base.op = IONIC_OP(dev->rdma_version, SEND);
0c894fc5e53316 Abhijit Gangurde 2025-04-23 899 break;
0c894fc5e53316 Abhijit Gangurde 2025-04-23 900 case IB_WR_SEND_WITH_IMM:
0c894fc5e53316 Abhijit Gangurde 2025-04-23 901 wqe->base.op = IONIC_OP(dev->rdma_version, SEND_IMM);
0c894fc5e53316 Abhijit Gangurde 2025-04-23 902 wqe->base.imm_data_key = wr->ex.imm_data;
0c894fc5e53316 Abhijit Gangurde 2025-04-23 903 break;
0c894fc5e53316 Abhijit Gangurde 2025-04-23 904 case IB_WR_SEND_WITH_INV:
0c894fc5e53316 Abhijit Gangurde 2025-04-23 905 wqe->base.op = IONIC_OP(dev->rdma_version, SEND_INV);
0c894fc5e53316 Abhijit Gangurde 2025-04-23 906 wqe->base.imm_data_key =
0c894fc5e53316 Abhijit Gangurde 2025-04-23 907 cpu_to_be32(wr->ex.invalidate_rkey);
0c894fc5e53316 Abhijit Gangurde 2025-04-23 908 break;
0c894fc5e53316 Abhijit Gangurde 2025-04-23 909 default:
0c894fc5e53316 Abhijit Gangurde 2025-04-23 910 return -EINVAL;
0c894fc5e53316 Abhijit Gangurde 2025-04-23 911 }
0c894fc5e53316 Abhijit Gangurde 2025-04-23 912
0c894fc5e53316 Abhijit Gangurde 2025-04-23 913 return ionic_prep_common(qp, wr, meta, wqe);
0c894fc5e53316 Abhijit Gangurde 2025-04-23 914 }
0c894fc5e53316 Abhijit Gangurde 2025-04-23 915
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-07 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202505072012.NkkKd0ba-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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