From: kernel test robot <lkp@intel.com>
To: Ahmed Zaki <ahmed.zaki@intel.com>, intel-wired-lan@lists.osuosl.org
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
przemyslaw.kitszel@intel.com, anthony.l.nguyen@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, almasrymina@google.com,
willemb@google.com, Ahmed Zaki <ahmed.zaki@intel.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 2/2] idpf: add flow steering support
Date: Tue, 25 Mar 2025 00:13:24 +0800 [thread overview]
Message-ID: <202503250010.XVQgpcvH-lkp@intel.com> (raw)
In-Reply-To: <20250324134939.253647-3-ahmed.zaki@intel.com>
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: i386-buildonly-randconfig-003-20250324 (https://download.01.org/0day-ci/archive/20250325/202503250010.XVQgpcvH-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250325/202503250010.XVQgpcvH-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/202503250010.XVQgpcvH-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'; have 'bool(struct idpf_vport *, u16)' {aka '_Bool(struct idpf_vport *, short unsigned int)'}
3532 | bool idpf_vport_is_cap_ena(struct idpf_vport *vport, u16 flag)
| ^~~~~~~~~~~~~~~~~~~~~
In file included from drivers/net/ethernet/intel/idpf/idpf.h:24,
from drivers/net/ethernet/intel/idpf/idpf_virtchnl.c:6:
drivers/net/ethernet/intel/idpf/idpf_virtchnl.h:108:6: note: previous declaration of 'idpf_vport_is_cap_ena' with type 'bool(struct idpf_vport *, u64)' {aka '_Bool(struct idpf_vport *, long long unsigned int)'}
108 | bool idpf_vport_is_cap_ena(struct idpf_vport *vport, u64 flag);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/net/ethernet/intel/idpf/idpf_virtchnl.c: In function 'idpf_sideband_flow_type_ena':
>> drivers/net/ethernet/intel/idpf/idpf_virtchnl.c:3560:77: error: expected ')' before ';' token
3560 | return !!(supp_ftypes & cpu_to_le64(VIRTCHNL2_FLOW_IPV4_UDP);
| ~ ^
>> drivers/net/ethernet/intel/idpf/idpf_virtchnl.c:3562:30: error: expected ';' before '}' token
3562 | return false;
| ^
| ;
3563 | }
| ~
>> drivers/net/ethernet/intel/idpf/idpf_virtchnl.c:3564:1: error: control reaches end of non-void function [-Werror=return-type]
3564 | }
| ^
cc1: some warnings being treated as errors
vim +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
next prev parent reply other threads:[~2025-03-24 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 13:49 [Intel-wired-lan] [PATCH iwl-next 0/2] idpf: add flow steering support Ahmed Zaki
2025-03-24 13:49 ` Ahmed Zaki
2025-03-24 13:49 ` [Intel-wired-lan] [PATCH iwl-next 1/2] virtchnl2: " Ahmed Zaki
2025-03-24 13:49 ` Ahmed Zaki
2025-03-24 13:49 ` [Intel-wired-lan] [PATCH iwl-next 2/2] idpf: " Ahmed Zaki
2025-03-24 13:49 ` Ahmed Zaki
2025-03-24 16:13 ` kernel test robot [this message]
2025-03-24 18:33 ` [Intel-wired-lan] " kernel test robot
2025-03-26 17:12 ` Alexander Lobakin
2025-03-26 17:14 ` [Intel-wired-lan] [PATCH iwl-next 0/2] " Alexander Lobakin
2025-03-26 17:36 ` Ahmed Zaki
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=202503250010.XVQgpcvH-lkp@intel.com \
--to=lkp@intel.com \
--cc=ahmed.zaki@intel.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=willemb@google.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 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.