All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, zhoujiadong <zhoujiadong5@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 3407/3407] drivers/scsi/huawei/hifc/hifc_dbgtool_knl.c:286:6: warning: no previous prototype for 'chipif_get_all_pf_dev_info'
Date: Sat, 13 Dec 2025 01:55:00 +0800	[thread overview]
Message-ID: <202512130114.JDMitdxe-lkp@intel.com> (raw)

tree:   https://gitee.com/openeuler/kernel.git OLK-5.10
head:   da8948fdddb84e5496272bab85973165594dd469
commit: 3d776c92130b1cdb4c9c0e5b7267152ab998fec3 [3407/3407] scsi/hifc: Fix compile error in allyesconfigs
config: x86_64-randconfig-001-20251212 (https://download.01.org/0day-ci/archive/20251213/202512130114.JDMitdxe-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/20251213/202512130114.JDMitdxe-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/202512130114.JDMitdxe-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/scsi/huawei/hifc/hifc_dbgtool_knl.c:286:6: warning: no previous prototype for 'chipif_get_all_pf_dev_info' [-Wmissing-prototypes]
     286 | void chipif_get_all_pf_dev_info(struct pf_dev_info *dev_info, int card_idx,
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~
--
   drivers/scsi/huawei/hifc/hifc_dbgtool_knl.c:797: warning: Function parameter or member 'vhwdev' not described in 'hifc_dbgtool_knl_init'
   drivers/scsi/huawei/hifc/hifc_dbgtool_knl.c:797: warning: Excess function parameter 'hwdev' description in 'hifc_dbgtool_knl_init'
>> drivers/scsi/huawei/hifc/hifc_dbgtool_knl.c:892: warning: Function parameter or member 'vhwdev' not described in 'hifc_dbgtool_knl_deinit'
>> drivers/scsi/huawei/hifc/hifc_dbgtool_knl.c:892: warning: Excess function parameter 'hwdev' description in 'hifc_dbgtool_knl_deinit'


vim +/chipif_get_all_pf_dev_info +286 drivers/scsi/huawei/hifc/hifc_dbgtool_knl.c

02b4d17a9ac62b denglei     2021-04-26  285  
02b4d17a9ac62b denglei     2021-04-26 @286  void chipif_get_all_pf_dev_info(struct pf_dev_info *dev_info, int card_idx,
02b4d17a9ac62b denglei     2021-04-26  287  				void **g_func_handle_array)
02b4d17a9ac62b denglei     2021-04-26  288  {
02b4d17a9ac62b denglei     2021-04-26  289  	u32 func_idx;
02b4d17a9ac62b denglei     2021-04-26  290  	struct hifc_hwdev *hwdev;
02b4d17a9ac62b denglei     2021-04-26  291  
02b4d17a9ac62b denglei     2021-04-26  292  	if (!dev_info) {
02b4d17a9ac62b denglei     2021-04-26  293  		pr_err("Params error!\n");
02b4d17a9ac62b denglei     2021-04-26  294  		return;
02b4d17a9ac62b denglei     2021-04-26  295  	}
02b4d17a9ac62b denglei     2021-04-26  296  
02b4d17a9ac62b denglei     2021-04-26  297  	/* pf at most 16 */
02b4d17a9ac62b denglei     2021-04-26  298  	for (func_idx = 0; func_idx < 16; func_idx++) {
02b4d17a9ac62b denglei     2021-04-26  299  		hwdev = (struct hifc_hwdev *)g_func_handle_array[func_idx];
02b4d17a9ac62b denglei     2021-04-26  300  
3d776c92130b1c zhoujiadong 2023-05-09  301  		dev_info[func_idx].phy_addr = g_hifc_card_phy_addr[card_idx];
02b4d17a9ac62b denglei     2021-04-26  302  
02b4d17a9ac62b denglei     2021-04-26  303  		if (!hwdev) {
02b4d17a9ac62b denglei     2021-04-26  304  			dev_info[func_idx].bar0_size = 0;
02b4d17a9ac62b denglei     2021-04-26  305  			dev_info[func_idx].bus = 0;
02b4d17a9ac62b denglei     2021-04-26  306  			dev_info[func_idx].slot = 0;
02b4d17a9ac62b denglei     2021-04-26  307  			dev_info[func_idx].func = 0;
02b4d17a9ac62b denglei     2021-04-26  308  		} else {
02b4d17a9ac62b denglei     2021-04-26  309  			dev_info[func_idx].bar0_size =
02b4d17a9ac62b denglei     2021-04-26  310  				pci_resource_len
02b4d17a9ac62b denglei     2021-04-26  311  				(((struct pci_dev *)hwdev->pcidev_hdl), 0);
02b4d17a9ac62b denglei     2021-04-26  312  			dev_info[func_idx].bus =
02b4d17a9ac62b denglei     2021-04-26  313  				((struct pci_dev *)
02b4d17a9ac62b denglei     2021-04-26  314  				hwdev->pcidev_hdl)->bus->number;
02b4d17a9ac62b denglei     2021-04-26  315  			dev_info[func_idx].slot =
02b4d17a9ac62b denglei     2021-04-26  316  				PCI_SLOT(((struct pci_dev *)hwdev->pcidev_hdl)
02b4d17a9ac62b denglei     2021-04-26  317  						->devfn);
02b4d17a9ac62b denglei     2021-04-26  318  			dev_info[func_idx].func =
02b4d17a9ac62b denglei     2021-04-26  319  				PCI_FUNC(((struct pci_dev *)hwdev->pcidev_hdl)
02b4d17a9ac62b denglei     2021-04-26  320  						->devfn);
02b4d17a9ac62b denglei     2021-04-26  321  		}
02b4d17a9ac62b denglei     2021-04-26  322  	}
02b4d17a9ac62b denglei     2021-04-26  323  }
02b4d17a9ac62b denglei     2021-04-26  324  

:::::: The code at line 286 was first introduced by commit
:::::: 02b4d17a9ac62b6d75e70a3d3bec5449bdeb30fa scsi/hifc: add port manager module of hifc driver

:::::: TO: denglei <denglei25@huawei.com>
:::::: CC: Zheng Zengkai <zhengzengkai@huawei.com>

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

                 reply	other threads:[~2025-12-12 17:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202512130114.JDMitdxe-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=zhoujiadong5@huawei.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.