netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bhargava Marreddy <bhargava.marreddy@broadcom.com>,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, michael.chan@broadcom.com,
	pavan.chebbi@broadcom.com, vsrama-krishna.nemani@broadcom.com,
	vikas.gupta@broadcom.com,
	Bhargava Marreddy <bhargava.marreddy@broadcom.com>,
	Rajashekar Hudumula <rajashekar.hudumula@broadcom.com>
Subject: Re: [net-next 05/12] bng_en: Add TX support
Date: Thu, 13 Nov 2025 12:53:21 +0800	[thread overview]
Message-ID: <202511131255.uExsPeUo-lkp@intel.com> (raw)
In-Reply-To: <20251111205829.97579-6-bhargava.marreddy@broadcom.com>

Hi Bhargava,

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/Bhargava-Marreddy/bng_en-Query-PHY-and-report-link-status/20251112-050616
base:   net-next/main
patch link:    https://lore.kernel.org/r/20251111205829.97579-6-bhargava.marreddy%40broadcom.com
patch subject: [net-next 05/12] bng_en: Add TX support
config: arc-randconfig-r122-20251113 (https://download.01.org/0day-ci/archive/20251113/202511131255.uExsPeUo-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251113/202511131255.uExsPeUo-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/202511131255.uExsPeUo-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/broadcom/bnge/bnge_txrx.c:717:11: sparse: sparse: symbol 'bnge_lhint_arr' was not declared. Should it be static?
   drivers/net/ethernet/broadcom/bnge/bnge_txrx.c: note: in included file (through include/net/net_namespace.h, include/linux/netdevice.h):
   include/linux/skbuff.h:2888:28: sparse: sparse: unsigned value that used to be signed checked against zero?
   include/linux/skbuff.h:2888:28: sparse: signed value source

vim +/bnge_lhint_arr +717 drivers/net/ethernet/broadcom/bnge/bnge_txrx.c

   716	
 > 717	const u16 bnge_lhint_arr[] = {
   718		TX_BD_FLAGS_LHINT_512_AND_SMALLER,
   719		TX_BD_FLAGS_LHINT_512_TO_1023,
   720		TX_BD_FLAGS_LHINT_1024_TO_2047,
   721		TX_BD_FLAGS_LHINT_1024_TO_2047,
   722		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   723		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   724		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   725		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   726		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   727		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   728		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   729		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   730		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   731		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   732		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   733		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   734		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   735		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   736		TX_BD_FLAGS_LHINT_2048_AND_LARGER,
   737	};
   738	

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

  parent reply	other threads:[~2025-11-13  4:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-11 20:57 [net-next 00/12] bng_en: enhancements for link, Rx/Tx, LRO/TPA & stats Bhargava Marreddy
2025-11-11 20:57 ` [net-next 01/12] bng_en: Query PHY and report link status Bhargava Marreddy
2025-11-11 20:57 ` [net-next 02/12] bng_en: Extend bnge_set_ring_params() for rx-copybreak Bhargava Marreddy
2025-11-11 20:57 ` [net-next 03/12] bng_en: Add RX support Bhargava Marreddy
2025-11-11 20:57 ` [net-next 04/12] bng_en: Handle an HWRM completion request Bhargava Marreddy
2025-11-11 20:57 ` [net-next 05/12] bng_en: Add TX support Bhargava Marreddy
2025-11-12 17:24   ` Jakub Kicinski
2025-11-13  4:53   ` kernel test robot [this message]
2025-11-11 20:57 ` [net-next 06/12] bng_en: Add support to handle AGG events Bhargava Marreddy
2025-11-12 17:23   ` Jakub Kicinski
2025-11-13  7:30   ` kernel test robot
2025-11-11 20:57 ` [net-next 07/12] bng_en: Add TPA related functions Bhargava Marreddy
2025-11-11 20:57 ` [net-next 08/12] bng_en: Add support for TPA events Bhargava Marreddy
2025-11-13  4:51   ` kernel test robot
2025-11-11 20:57 ` [net-next 09/12] bng_en: Add ethtool link settings and capabilities support Bhargava Marreddy
2025-11-11 20:58 ` [net-next 10/12] bng_en: Add initial support for ethtool stats display Bhargava Marreddy
2025-11-11 20:58 ` [net-next 11/12] bng_en: Create per-PF workqueue and timer for asynchronous events Bhargava Marreddy
2025-11-11 20:58 ` [net-next 12/12] bng_en: Query firmware for statistics and accumulate Bhargava Marreddy

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=202511131255.uExsPeUo-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bhargava.marreddy@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=pavan.chebbi@broadcom.com \
    --cc=rajashekar.hudumula@broadcom.com \
    --cc=vikas.gupta@broadcom.com \
    --cc=vsrama-krishna.nemani@broadcom.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).