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,
Bhargava Marreddy <bhargava.marreddy@broadcom.com>,
Vikas Gupta <vikas.gupta@broadcom.com>,
Rajashekar Hudumula <rajashekar.hudumula@broadcom.com>
Subject: Re: [net-next 7/9] bng_en: Register rings with the firmware
Date: Thu, 14 Aug 2025 14:47:16 +0800 [thread overview]
Message-ID: <202508141404.DrfpnTy0-lkp@intel.com> (raw)
In-Reply-To: <20250813215603.76526-8-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-Add-initial-support-for-RX-and-TX-rings/20250814-004339
base: net-next/main
patch link: https://lore.kernel.org/r/20250813215603.76526-8-bhargava.marreddy%40broadcom.com
patch subject: [net-next 7/9] bng_en: Register rings with the firmware
config: loongarch-randconfig-r073-20250814 (https://download.01.org/0day-ci/archive/20250814/202508141404.DrfpnTy0-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 3769ce013be2879bf0b329c14a16f5cb766f26ce)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250814/202508141404.DrfpnTy0-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/202508141404.DrfpnTy0-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ethernet/broadcom/bnge/bnge_hwrm_lib.c:768:32: warning: variable 'resp' set but not used [-Wunused-but-set-variable]
768 | struct hwrm_ring_free_output *resp;
| ^
1 warning generated.
vim +/resp +768 drivers/net/ethernet/broadcom/bnge/bnge_hwrm_lib.c
763
764 int hwrm_ring_free_send_msg(struct bnge_net *bn,
765 struct bnge_ring_struct *ring,
766 u32 ring_type, int cmpl_ring_id)
767 {
> 768 struct hwrm_ring_free_output *resp;
769 struct hwrm_ring_free_input *req;
770 struct bnge_dev *bd = bn->bd;
771 int rc;
772
773 rc = bnge_hwrm_req_init(bd, req, HWRM_RING_FREE);
774 if (rc)
775 goto exit;
776
777 req->cmpl_ring = cpu_to_le16(cmpl_ring_id);
778 req->ring_type = ring_type;
779 req->ring_id = cpu_to_le16(ring->fw_ring_id);
780
781 resp = bnge_hwrm_req_hold(bd, req);
782 rc = bnge_hwrm_req_send(bd, req);
783 bnge_hwrm_req_drop(bd, req);
784 exit:
785 if (rc) {
786 netdev_err(bd->netdev, "hwrm_ring_free type %d failed. rc:%d\n", ring_type, rc);
787 return -EIO;
788 }
789 return 0;
790 }
791
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-14 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 21:55 [net-next 0/9] Add more functionality to BNGE Bhargava Marreddy
2025-08-13 21:55 ` [net-next 1/9] bng_en: Add initial support for RX and TX rings Bhargava Marreddy
2025-08-14 5:32 ` kernel test robot
2025-08-13 21:55 ` [net-next 2/9] bng_en: Add initial support for CP and NQ rings Bhargava Marreddy
2025-08-13 21:55 ` [net-next 3/9] bng_en: Introduce VNIC Bhargava Marreddy
2025-08-13 21:55 ` [net-next 4/9] bng_en: Initialise core resources Bhargava Marreddy
2025-08-13 21:55 ` [net-next 5/9] bng_en: Allocate packet buffers Bhargava Marreddy
2025-08-13 21:56 ` [net-next 6/9] bng_en: Allocate stat contexts Bhargava Marreddy
2025-08-13 21:56 ` [net-next 7/9] bng_en: Register rings with the firmware Bhargava Marreddy
2025-08-14 6:47 ` kernel test robot [this message]
2025-08-14 7:54 ` kernel test robot
2025-08-13 21:56 ` [net-next 8/9] bng_en: Register default VNIC Bhargava Marreddy
2025-08-13 21:56 ` [net-next 9/9] bng_en: Configure " 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=202508141404.DrfpnTy0-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 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.