public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dong Yibo <dong100@mucse.com>,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, danishanwar@ti.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, dong100@mucse.com
Subject: Re: [PATCH net-next 4/4] net: rnpgbe: Add link status handling support
Date: Thu, 26 Mar 2026 12:46:05 +0800	[thread overview]
Message-ID: <202603261216.IjF1gt9b-lkp@intel.com> (raw)
In-Reply-To: <20260325091204.94015-5-dong100@mucse.com>

Hi Dong,

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/Dong-Yibo/net-rnpgbe-Add-interrupt-handling/20260326-025137
base:   net-next/main
patch link:    https://lore.kernel.org/r/20260325091204.94015-5-dong100%40mucse.com
patch subject: [PATCH net-next 4/4] net: rnpgbe: Add link status handling support
config: x86_64-randconfig-002-20260326 (https://download.01.org/0day-ci/archive/20260326/202603261216.IjF1gt9b-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260326/202603261216.IjF1gt9b-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/202603261216.IjF1gt9b-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: drivers/net/ethernet/mucse/rnpgbe/rnpgbe_mbx_fw.c:233 function parameter 'is_report' not described in 'mucse_mbx_link_report'
>> Warning: drivers/net/ethernet/mucse/rnpgbe/rnpgbe_mbx_fw.c:313 function parameter 'hw' not described in 'mucse_mbx_fw_req_handler'
>> Warning: drivers/net/ethernet/mucse/rnpgbe/rnpgbe_mbx_fw.c:233 function parameter 'is_report' not described in 'mucse_mbx_link_report'
>> Warning: drivers/net/ethernet/mucse/rnpgbe/rnpgbe_mbx_fw.c:313 function parameter 'hw' not described in 'mucse_mbx_fw_req_handler'
--
>> Warning: drivers/net/ethernet/mucse/rnpgbe/rnpgbe_lib.c:1888 expecting prototype for mucse_watchdog_subtask(). Prototype was for rnpgbe_watchdog_subtask() instead

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

      reply	other threads:[~2026-03-26  4:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25  9:12 [PATCH net-next 0/4] net: rnpgbe: Add TX/RX and link status support Dong Yibo
2026-03-25  9:12 ` [PATCH net-next 1/4] net: rnpgbe: Add interrupt handling Dong Yibo
2026-03-25  9:12 ` [PATCH net-next 2/4] net: rnpgbe: Add basic TX packet transmission support Dong Yibo
2026-03-25  9:12 ` [PATCH net-next 3/4] net: rnpgbe: Add RX packet reception support Dong Yibo
2026-03-25  9:12 ` [PATCH net-next 4/4] net: rnpgbe: Add link status handling support Dong Yibo
2026-03-26  4:46   ` 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=202603261216.IjF1gt9b-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=dong100@mucse.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.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