From: kernel test robot <lkp@intel.com>
To: Larysa Zaremba <larysa.zaremba@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: oe-kbuild-all@lists.linux.dev,
Larysa Zaremba <larysa.zaremba@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Mateusz Pacuszka <mateuszx.pacuszka@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 6/6] ice: enable LLDP TX for VFs through tc
Date: Wed, 5 Feb 2025 11:29:49 +0800 [thread overview]
Message-ID: <202502051116.UJMCGQWA-lkp@intel.com> (raw)
In-Reply-To: <20250204115111.1652453-7-larysa.zaremba@intel.com>
Hi Larysa,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tnguy-next-queue/dev-queue]
url: https://github.com/intel-lab-lkp/linux/commits/Larysa-Zaremba/ice-fix-check-for-existing-switch-rule/20250204-200839
base: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
patch link: https://lore.kernel.org/r/20250204115111.1652453-7-larysa.zaremba%40intel.com
patch subject: [Intel-wired-lan] [PATCH iwl-next v2 6/6] ice: enable LLDP TX for VFs through tc
config: csky-randconfig-r132-20250205 (https://download.01.org/0day-ci/archive/20250205/202502051116.UJMCGQWA-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250205/202502051116.UJMCGQWA-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/202502051116.UJMCGQWA-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/intel/ice/ice_tc_lib.c:848:18: sparse: sparse: Initializer entry defined twice
drivers/net/ethernet/intel/ice/ice_tc_lib.c:854:18: sparse: also defined here
vim +848 drivers/net/ethernet/intel/ice/ice_tc_lib.c
843
844 int ice_drop_vf_tx_lldp(struct ice_vsi *vsi, bool init)
845 {
846 struct ice_rule_query_data rule_added;
847 struct ice_adv_rule_info rinfo = {
> 848 .sw_act = {
849 .fltr_act = ICE_DROP_PACKET,
850 .flag = ICE_FLTR_TX,
851 },
852 .priority = 7,
853 .flags_info.act_valid = true,
854 .sw_act.src = vsi->idx,
855 .src_vsi = vsi->idx,
856 .sw_act.vsi_handle = vsi->idx,
857 };
858 struct ice_adv_lkup_elem list[3];
859 struct ice_pf *pf = vsi->back;
860 int err;
861
862 if (!init && !vsi->vf->lldp_tx_ena)
863 return 0;
864
865 ice_rule_add_direction_metadata(&list[0]);
866 ice_rule_add_src_vsi_metadata(&list[1]);
867 list[2].type = ICE_ETYPE_OL;
868 list[2].h_u.ethertype.ethtype_id = htons(ETH_P_LLDP);
869 list[2].m_u.ethertype.ethtype_id = htons(0xFFFF);
870
871 err = ice_add_adv_rule(&pf->hw, list, ARRAY_SIZE(list), &rinfo,
872 &rule_added);
873 if (err) {
874 dev_err(&pf->pdev->dev,
875 "Failed to add an LLDP rule to VSI 0x%X: %d\n",
876 vsi->idx, err);
877 } else {
878 vsi->vf->lldp_recipe_id = rule_added.rid;
879 vsi->vf->lldp_rule_id = rule_added.rule_id;
880 vsi->vf->lldp_tx_ena = false;
881 }
882
883 return err;
884 }
885
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-02-05 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 11:50 [PATCH iwl-next v2 0/6] ice: LLDP support for VFs Larysa Zaremba
2025-02-04 11:50 ` [PATCH iwl-next v2 1/6] ice: fix check for existing switch rule Larysa Zaremba
2025-02-04 11:50 ` [PATCH iwl-next v2 2/6] ice: do not add LLDP-specific filter if not necessary Larysa Zaremba
2025-02-04 11:50 ` [PATCH iwl-next v2 3/6] ice: receive LLDP on trusted VFs Larysa Zaremba
2025-02-04 11:50 ` [PATCH iwl-next v2 4/6] ice: remove headers argument from ice_tc_count_lkups Larysa Zaremba
2025-02-04 11:50 ` [PATCH iwl-next v2 5/6] ice: support egress drop rules on PF Larysa Zaremba
2025-02-04 11:50 ` [PATCH iwl-next v2 6/6] ice: enable LLDP TX for VFs through tc Larysa Zaremba
2025-02-05 3:29 ` kernel test robot [this message]
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=202502051116.UJMCGQWA-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mateuszx.pacuszka@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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