linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Prabhakar Kushwaha <pkushwaha@marvell.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Ariel Elior <aelior@marvell.com>, Shai Malin <smalin@marvell.com>,
	Omkar Kulkarni <okulkarni@marvell.com>
Subject: [linux-next:master 4975/7405] drivers/net/ethernet/qlogic/qed/qed_dev.c:2410:24: error: implicit declaration of function 'qed_sriov_eqe_event'; did you mean 'qed_common_eqe_event'?
Date: Mon, 11 Oct 2021 18:55:03 +0800	[thread overview]
Message-ID: <202110111854.vYYhOUAq-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3752 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   d3134eb5de8546a214c028fb7195e764b89da7d4
commit: fe40a830dcded26f012739fd6dac0da9c805bc38 [4975/7405] qed: Update qed_hsi.h for fw 8.59.1.0
config: s390-randconfig-r044-20211011 (attached as .config)
compiler: s390-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=fe40a830dcded26f012739fd6dac0da9c805bc38
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout fe40a830dcded26f012739fd6dac0da9c805bc38
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=s390 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

Note: the linux-next/master HEAD d3134eb5de8546a214c028fb7195e764b89da7d4 builds fine.
      It may have been fixed somewhere.

All errors (new ones prefixed by >>):

   drivers/net/ethernet/qlogic/qed/qed_dev.c: In function 'qed_fw_err_handler':
   drivers/net/ethernet/qlogic/qed/qed_dev.c:2390:17: error: implicit declaration of function 'qed_sriov_vfpf_malicious' [-Werror=implicit-function-declaration]
    2390 |                 qed_sriov_vfpf_malicious(p_hwfn, &data->err_data);
         |                 ^~~~~~~~~~~~~~~~~~~~~~~~
   drivers/net/ethernet/qlogic/qed/qed_dev.c: In function 'qed_common_eqe_event':
>> drivers/net/ethernet/qlogic/qed/qed_dev.c:2410:24: error: implicit declaration of function 'qed_sriov_eqe_event'; did you mean 'qed_common_eqe_event'? [-Werror=implicit-function-declaration]
    2410 |                 return qed_sriov_eqe_event(p_hwfn, opcode, echo, data,
         |                        ^~~~~~~~~~~~~~~~~~~
         |                        qed_common_eqe_event
   cc1: some warnings being treated as errors


vim +2410 drivers/net/ethernet/qlogic/qed/qed_dev.c

  2379	
  2380	static int qed_fw_err_handler(struct qed_hwfn *p_hwfn,
  2381				      u8 opcode,
  2382				      u16 echo,
  2383				      union event_ring_data *data, u8 fw_return_code)
  2384	{
  2385		if (fw_return_code != COMMON_ERR_CODE_ERROR)
  2386			goto eqe_unexpected;
  2387	
  2388		if (data->err_data.recovery_scope == ERR_SCOPE_FUNC &&
  2389		    le16_to_cpu(data->err_data.entity_id) >= MAX_NUM_PFS) {
> 2390			qed_sriov_vfpf_malicious(p_hwfn, &data->err_data);
  2391			return 0;
  2392		}
  2393	
  2394	eqe_unexpected:
  2395		DP_ERR(p_hwfn,
  2396		       "Skipping unexpected eqe 0x%02x, FW return code 0x%x, echo 0x%x\n",
  2397		       opcode, fw_return_code, echo);
  2398		return -EINVAL;
  2399	}
  2400	
  2401	static int qed_common_eqe_event(struct qed_hwfn *p_hwfn,
  2402					u8 opcode,
  2403					__le16 echo,
  2404					union event_ring_data *data,
  2405					u8 fw_return_code)
  2406	{
  2407		switch (opcode) {
  2408		case COMMON_EVENT_VF_PF_CHANNEL:
  2409		case COMMON_EVENT_VF_FLR:
> 2410			return qed_sriov_eqe_event(p_hwfn, opcode, echo, data,
  2411						   fw_return_code);
  2412		case COMMON_EVENT_FW_ERROR:
  2413			return qed_fw_err_handler(p_hwfn, opcode,
  2414						  le16_to_cpu(echo), data,
  2415						  fw_return_code);
  2416		default:
  2417			DP_INFO(p_hwfn->cdev, "Unknown eqe event 0x%02x, echo 0x%x\n",
  2418				opcode, echo);
  2419			return -EINVAL;
  2420		}
  2421	}
  2422	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38140 bytes --]

             reply	other threads:[~2021-10-11 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 10:55 kernel test robot [this message]
2021-10-11 11:12 Prabhakar Kushwaha

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=202110111854.vYYhOUAq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aelior@marvell.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=okulkarni@marvell.com \
    --cc=pkushwaha@marvell.com \
    --cc=smalin@marvell.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