[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202503250234.USFLMuAQ-lkp@intel.com>
Date: Tue, 25 Mar 2025 02:33:20 +0800
From: kernel test robot <lkp@...el.com>
To: Ahmed Zaki <ahmed.zaki@...el.com>, intel-wired-lan@...ts.osuosl.org
Cc: llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
netdev@...r.kernel.org, przemyslaw.kitszel@...el.com,
anthony.l.nguyen@...el.com, andrew+netdev@...n.ch,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, almasrymina@...gle.com, willemb@...gle.com,
Ahmed Zaki <ahmed.zaki@...el.com>,
Sridhar Samudrala <sridhar.samudrala@...el.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 2/2] idpf: add flow steering
support
Hi Ahmed,
kernel test robot noticed the following build errors:
[auto build test ERROR on tnguy-next-queue/dev-queue]
url: https://github.com/intel-lab-lkp/linux/commits/Ahmed-Zaki/virtchnl2-add-flow-steering-support/20250324-215138
base: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
patch link: https://lore.kernel.org/r/20250324134939.253647-3-ahmed.zaki%40intel.com
patch subject: [Intel-wired-lan] [PATCH iwl-next 2/2] idpf: add flow steering support
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250325/202503250234.USFLMuAQ-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250325/202503250234.USFLMuAQ-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503250234.USFLMuAQ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/net/ethernet/intel/idpf/idpf_virtchnl.c:3532:6: error: conflicting types for 'idpf_vport_is_cap_ena'
3532 | bool idpf_vport_is_cap_ena(struct idpf_vport *vport, u16 flag)
| ^
drivers/net/ethernet/intel/idpf/idpf_virtchnl.h:108:6: note: previous declaration is here
108 | bool idpf_vport_is_cap_ena(struct idpf_vport *vport, u64 flag);
| ^
>> drivers/net/ethernet/intel/idpf/idpf_virtchnl.c:3560:63: error: expected ')'
3560 | return !!(supp_ftypes & cpu_to_le64(VIRTCHNL2_FLOW_IPV4_UDP);
| ^
drivers/net/ethernet/intel/idpf/idpf_virtchnl.c:3560:12: note: to match this '('
3560 | return !!(supp_ftypes & cpu_to_le64(VIRTCHNL2_FLOW_IPV4_UDP);
| ^
2 errors generated.
vim +/idpf_vport_is_cap_ena +3532 drivers/net/ethernet/intel/idpf/idpf_virtchnl.c
3524
3525 /**
3526 * idpf_vport_is_cap_ena - Check if vport capability is enabled
3527 * @vport: Private data struct
3528 * @flag: flag(s) to check
3529 *
3530 * Return true if the capability is supported, false otherwise
3531 */
> 3532 bool idpf_vport_is_cap_ena(struct idpf_vport *vport, u16 flag)
3533 {
3534 struct virtchnl2_create_vport *vport_msg;
3535
3536 vport_msg = vport->adapter->vport_params_recvd[vport->idx];
3537
3538 return !!(vport_msg->vport_flags & le16_to_cpu(flag));
3539 }
3540
3541 /**
3542 * idpf_sideband_flow_type_ena - Check if steering is enabled for flow type
3543 * @vport: Private data struct
3544 * @flow_type: flow type to check (from ethtool.h)
3545 *
3546 * Return true if sideband filters are allowed for @flow_type, false otherwise
3547 */
3548 bool idpf_sideband_flow_type_ena(struct idpf_vport *vport, u32 flow_type)
3549 {
3550 struct virtchnl2_create_vport *vport_msg;
3551 __le64 supp_ftypes;
3552
3553 vport_msg = vport->adapter->vport_params_recvd[vport->idx];
3554 supp_ftypes = vport_msg->sideband_flow_types;
3555
3556 switch (flow_type) {
3557 case TCP_V4_FLOW:
3558 return !!(supp_ftypes & cpu_to_le64(VIRTCHNL2_FLOW_IPV4_TCP));
3559 case UDP_V4_FLOW:
> 3560 return !!(supp_ftypes & cpu_to_le64(VIRTCHNL2_FLOW_IPV4_UDP);
3561 default:
3562 return false;
3563 }
3564 }
3565
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists