netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Vasundhara Volam <vasundhara-v.volam@broadcom.com>, jeyu@kernel.org
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
	davem@davemloft.net, netdev@vger.kernel.org,
	michael.chan@broadcom.com,
	Vasundhara Volam <vasundhara-v.volam@broadcom.com>,
	Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [PATCH v2] bnxt_en: use new module_firmware_crashed()
Date: Sat, 16 May 2020 21:30:09 +0800	[thread overview]
Message-ID: <202005162108.tCWQJ2C9%lkp@intel.com> (raw)
In-Reply-To: <1589617529-24009-1-git-send-email-vasundhara-v.volam@broadcom.com>

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

Hi Vasundhara,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on sparc-next/master]
[also build test ERROR on linus/master v5.7-rc5 next-20200515]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Vasundhara-Volam/bnxt_en-use-new-module_firmware_crashed/20200516-163022
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-next.git master
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 13d44b2a0c7ef404b13b16644765977cd5310fe2)
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install x86_64 cross compiling tool for clang build
        # apt-get install binutils-x86-64-linux-gnu
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 

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

All errors (new ones prefixed by >>, old ones prefixed by <<):

>> drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c:124:2: error: implicit declaration of function 'module_firmware_crashed' [-Werror,-Wimplicit-function-declaration]
module_firmware_crashed();
^
1 error generated.

vim +/module_firmware_crashed +124 drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c

   112	
   113	static int bnxt_fw_fatal_recover(struct devlink_health_reporter *reporter,
   114					 void *priv_ctx,
   115					 struct netlink_ext_ack *extack)
   116	{
   117		struct bnxt *bp = devlink_health_reporter_priv(reporter);
   118		struct bnxt_fw_reporter_ctx *fw_reporter_ctx = priv_ctx;
   119		unsigned long event;
   120	
   121		if (!priv_ctx)
   122			return -EOPNOTSUPP;
   123	
 > 124		module_firmware_crashed();
   125		bp->fw_health->fatal = true;
   126		event = fw_reporter_ctx->sp_event;
   127		if (event == BNXT_FW_RESET_NOTIFY_SP_EVENT)
   128			bnxt_fw_reset(bp);
   129		else if (event == BNXT_FW_EXCEPTION_SP_EVENT)
   130			bnxt_fw_exception(bp);
   131	
   132		return -EINPROGRESS;
   133	}
   134	

---
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: 73419 bytes --]

      parent reply	other threads:[~2020-05-16 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16  8:25 [PATCH v2] bnxt_en: use new module_firmware_crashed() Vasundhara Volam
2020-05-16 12:55 ` kbuild test robot
2020-05-16 13:30 ` kbuild 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=202005162108.tCWQJ2C9%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=davem@davemloft.net \
    --cc=jeyu@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=mcgrof@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=vasundhara-v.volam@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).