All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mengyuan Lou <mengyuanlou@net-swift.com>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	jiawenwu@trustnetic.com, duanqiangwen@net-swift.com,
	Mengyuan Lou <mengyuanlou@net-swift.com>
Subject: Re: [PATCH net-next v3 5/6] net: ngbe: add sriov function support
Date: Thu, 16 May 2024 08:46:27 +0800	[thread overview]
Message-ID: <202405160844.t8jS88dy-lkp@intel.com> (raw)
In-Reply-To: <15515521993762EE+20240515100830.32920-6-mengyuanlou@net-swift.com>

Hi Mengyuan,

kernel test robot noticed the following build warnings:

[auto build test WARNING on net-next/main]

url:    https://github.com/intel-lab-lkp/linux/commits/Mengyuan-Lou/net-libwx-Add-sriov-api-for-wangxun-nics/20240515-185015
base:   net-next/main
patch link:    https://lore.kernel.org/r/15515521993762EE%2B20240515100830.32920-6-mengyuanlou%40net-swift.com
patch subject: [PATCH net-next v3 5/6] net: ngbe: add sriov function support
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240516/202405160844.t8jS88dy-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240516/202405160844.t8jS88dy-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/202405160844.t8jS88dy-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/net/ethernet/wangxun/libwx/wx_sriov.c:999:17: warning: variable 'i' is uninitialized when used here [-Wuninitialized]
     999 |         if (wx->vfinfo[i].clear_to_send)
         |                        ^
   drivers/net/ethernet/wangxun/libwx/wx_sriov.c:992:7: note: initialize the variable 'i' to silence this warning
     992 |         u16 i;
         |              ^
         |               = 0
   drivers/net/ethernet/wangxun/libwx/wx_sriov.c:312:20: warning: unused function 'wx_ping_vf' [-Wunused-function]
     312 | static inline void wx_ping_vf(struct wx *wx, int vf)
         |                    ^~~~~~~~~~
   2 warnings generated.


vim +/i +999 drivers/net/ethernet/wangxun/libwx/wx_sriov.c

   988	
   989	void wx_ping_all_vfs_with_link_status(struct wx *wx, bool link_up)
   990	{
   991		u32 msgbuf[2] = {0, 0};
   992		u16 i;
   993	
   994		if (!wx->num_vfs)
   995			return;
   996		msgbuf[0] = WX_PF_NOFITY_VF_LINK_STATUS | WX_PF_CONTROL_MSG;
   997		if (link_up)
   998			msgbuf[1] = (wx->speed << 1) | link_up;
 > 999		if (wx->vfinfo[i].clear_to_send)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2024-05-16  0:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240515100830.32920-1-mengyuanlou@net-swift.com>
2024-05-15  9:50 ` [PATCH net-next v3 1/6] net: libwx: Add malibox api for wangxun pf drivers Mengyuan Lou
2024-05-15 15:28   ` Simon Horman
2024-05-15  9:50 ` [PATCH net-next v3 2/6] net: libwx: Add sriov api for wangxun nics Mengyuan Lou
2024-05-15  9:50 ` [PATCH net-next v3 3/6] net: libwx: Redesign flow when sriov is enabled Mengyuan Lou
2024-05-15  9:50 ` [PATCH net-next v3 4/6] net: libwx: Add msg task func Mengyuan Lou
2024-05-15 15:24   ` Simon Horman
2024-05-15  9:50 ` [PATCH net-next v3 5/6] net: ngbe: add sriov function support Mengyuan Lou
2024-05-15 15:22   ` Simon Horman
2024-05-16  0:46   ` kernel test robot [this message]
2024-05-15  9:50 ` [PATCH net-next v3 6/6] net: txgbe: " Mengyuan Lou
     [not found] <20240415110225.75132-1-mengyuanlou@net-swift.com>
2024-04-15 10:54 ` [PATCH net-next v3 5/6] net: ngbe: " Mengyuan Lou

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=202405160844.t8jS88dy-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=duanqiangwen@net-swift.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=llvm@lists.linux.dev \
    --cc=mengyuanlou@net-swift.com \
    --cc=netdev@vger.kernel.org \
    --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 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.