From: kernel test robot <lkp@intel.com>
To: Piotr Kwapulinski <piotr.kwapulinski@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: oe-kbuild-all@lists.linux.dev,
Piotr Kwapulinski <piotr.kwapulinski@intel.com>,
netdev@vger.kernel.org,
Carolyn Wyborny <carolyn.wyborny@intel.com>,
Jan Glaza <jan.glaza@intel.com>,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 5/5] ixgbe: Enable link management in E610 device
Date: Thu, 28 Mar 2024 06:12:14 +0800 [thread overview]
Message-ID: <202403280523.pcRsyVNp-lkp@intel.com> (raw)
In-Reply-To: <20240327155422.25424-6-piotr.kwapulinski@intel.com>
Hi Piotr,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.8]
[cannot apply to tnguy-next-queue/dev-queue tnguy-net-queue/dev-queue horms-ipvs/master v6.9-rc1 linus/master next-20240327]
[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/Piotr-Kwapulinski/ixgbe-Add-support-for-E610-FW-Admin-Command-Interface/20240327-234237
base: v6.8
patch link: https://lore.kernel.org/r/20240327155422.25424-6-piotr.kwapulinski%40intel.com
patch subject: [Intel-wired-lan] [PATCH iwl-next v1 5/5] ixgbe: Enable link management in E610 device
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20240328/202403280523.pcRsyVNp-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240328/202403280523.pcRsyVNp-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/202403280523.pcRsyVNp-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c:2822:5: warning: no previous prototype for 'ixgbe_set_fw_drv_ver_x550' [-Wmissing-prototypes]
2822 | s32 ixgbe_set_fw_drv_ver_x550(struct ixgbe_hw *hw, u8 maj, u8 min,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c:3563:6: warning: no previous prototype for 'ixgbe_set_ethertype_anti_spoofing_x550' [-Wmissing-prototypes]
3563 | void ixgbe_set_ethertype_anti_spoofing_x550(struct ixgbe_hw *hw,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c:3584:6: warning: no previous prototype for 'ixgbe_set_source_address_pruning_x550' [-Wmissing-prototypes]
3584 | void ixgbe_set_source_address_pruning_x550(struct ixgbe_hw *hw,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/ixgbe_set_ethertype_anti_spoofing_x550 +3563 drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c
3556
3557 /** ixgbe_set_ethertype_anti_spoofing_x550 - Enable/Disable Ethertype
3558 * anti-spoofing
3559 * @hw: pointer to hardware structure
3560 * @enable: enable or disable switch for Ethertype anti-spoofing
3561 * @vf: Virtual Function pool - VF Pool to set for Ethertype anti-spoofing
3562 **/
> 3563 void ixgbe_set_ethertype_anti_spoofing_x550(struct ixgbe_hw *hw,
3564 bool enable, int vf)
3565 {
3566 int vf_target_reg = vf >> 3;
3567 int vf_target_shift = vf % 8 + IXGBE_SPOOF_ETHERTYPEAS_SHIFT;
3568 u32 pfvfspoof;
3569
3570 pfvfspoof = IXGBE_READ_REG(hw, IXGBE_PFVFSPOOF(vf_target_reg));
3571 if (enable)
3572 pfvfspoof |= BIT(vf_target_shift);
3573 else
3574 pfvfspoof &= ~BIT(vf_target_shift);
3575
3576 IXGBE_WRITE_REG(hw, IXGBE_PFVFSPOOF(vf_target_reg), pfvfspoof);
3577 }
3578
3579 /** ixgbe_set_source_address_pruning_x550 - Enable/Disbale src address pruning
3580 * @hw: pointer to hardware structure
3581 * @enable: enable or disable source address pruning
3582 * @pool: Rx pool to set source address pruning for
3583 **/
> 3584 void ixgbe_set_source_address_pruning_x550(struct ixgbe_hw *hw,
3585 bool enable,
3586 unsigned int pool)
3587 {
3588 u64 pfflp;
3589
3590 /* max rx pool is 63 */
3591 if (pool > 63)
3592 return;
3593
3594 pfflp = (u64)IXGBE_READ_REG(hw, IXGBE_PFFLPL);
3595 pfflp |= (u64)IXGBE_READ_REG(hw, IXGBE_PFFLPH) << 32;
3596
3597 if (enable)
3598 pfflp |= (1ULL << pool);
3599 else
3600 pfflp &= ~(1ULL << pool);
3601
3602 IXGBE_WRITE_REG(hw, IXGBE_PFFLPL, (u32)pfflp);
3603 IXGBE_WRITE_REG(hw, IXGBE_PFFLPH, (u32)(pfflp >> 32));
3604 }
3605
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-03-27 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 15:54 [PATCH iwl-next v1 0/5] ixgbe: Add support for Intel(R) E610 device Piotr Kwapulinski
2024-03-27 15:54 ` [PATCH iwl-next v1 1/5] ixgbe: Add support for E610 FW Admin Command Interface Piotr Kwapulinski
2024-03-29 18:28 ` Simon Horman
2024-04-03 7:27 ` Kwapulinski, Piotr
2024-04-05 0:03 ` [Intel-wired-lan] " Vinicius Costa Gomes
2024-04-05 14:35 ` Kwapulinski, Piotr
2024-04-05 16:40 ` Vinicius Costa Gomes
2024-03-27 15:54 ` [PATCH iwl-next v1 2/5] ixgbe: Add support for E610 device capabilities detection Piotr Kwapulinski
2024-03-27 15:54 ` [PATCH iwl-next v1 3/5] ixgbe: Add link management support for E610 device Piotr Kwapulinski
2024-04-05 0:14 ` [Intel-wired-lan] " Vinicius Costa Gomes
2024-04-05 15:10 ` Kwapulinski, Piotr
2024-03-27 15:54 ` [PATCH iwl-next v1 4/5] ixgbe: Add support for NVM handling in " Piotr Kwapulinski
2024-03-27 15:54 ` [PATCH iwl-next v1 5/5] ixgbe: Enable link management " Piotr Kwapulinski
2024-03-27 22:12 ` kernel test robot [this message]
2024-03-28 0:58 ` [Intel-wired-lan] " kernel test robot
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=202403280523.pcRsyVNp-lkp@intel.com \
--to=lkp@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jan.glaza@intel.com \
--cc=jedrzej.jagielski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=piotr.kwapulinski@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;
as well as URLs for NNTP newsgroup(s).