public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Nilesh Javali <njavali@marvell.com>, martin.petersen@oracle.com
Cc: kbuild-all@lists.01.org, linux-scsi@vger.kernel.org,
	GR-QLogic-Storage-Upstream@marvell.com
Subject: Re: [PATCH 03/12] qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices
Date: Wed, 19 Aug 2020 05:12:59 +0800	[thread overview]
Message-ID: <202008190517.dxLmqIFK%lkp@intel.com> (raw)
In-Reply-To: <20200818123203.20361-4-njavali@marvell.com>

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

Hi Nilesh,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on dca93232b361d260413933903cd4bdbd92ebcc7f]

url:    https://github.com/0day-ci/linux/commits/Nilesh-Javali/qla2xxx-misc-features-and-bug-fixes/20200818-203851
base:    dca93232b361d260413933903cd4bdbd92ebcc7f
config: x86_64-kexec (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

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

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

>> ERROR: modpost: "nvme_fc_set_remoteport_devloss" [drivers/scsi/qla2xxx/qla2xxx.ko] undefined!

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

  parent reply	other threads:[~2020-08-18 21:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 12:31 [PATCH 00/12] qla2xxx misc features and bug fixes Nilesh Javali
2020-08-18 12:31 ` [PATCH 01/12] qla2xxx: Fix I/O failures during remote port toggle testing Nilesh Javali
2020-08-18 12:31 ` [PATCH 02/12] qla2xxx: Setup debugfs entries for remote ports Nilesh Javali
2020-08-18 12:31 ` [PATCH 03/12] qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices Nilesh Javali
2020-08-18 13:24   ` Roman Bolshakov
2020-08-19 22:09     ` Arun Easi
2020-08-18 21:04   ` kernel test robot
2020-08-18 21:12   ` kernel test robot [this message]
2020-08-18 12:31 ` [PATCH 04/12] qla2xxx: Honor status qualifier in FCP_RSP per spec Nilesh Javali
2020-08-18 12:31 ` [PATCH 05/12] qla2xxx: Reduce duplicate code in reporting speed Nilesh Javali
2020-08-18 12:31 ` [PATCH 06/12] qla2xxx: Fix memory size truncation Nilesh Javali
2020-08-18 12:31 ` [PATCH 07/12] qla2xxx: performance tweak Nilesh Javali
2020-08-18 12:31 ` [PATCH 08/12] qla2xxx: Fix I/O errors during LIP reset tests Nilesh Javali
2020-08-18 12:32 ` [PATCH 09/12] qla2xxx: Make tgt_port_database available in initiator mode Nilesh Javali
2020-08-18 12:32 ` [PATCH 10/12] qla2xxx: Add rport fields in debugfs Nilesh Javali
2020-08-18 12:32 ` [PATCH 11/12] qla2xxx: Add IOCB resource tracking Nilesh Javali
2020-08-18 12:32 ` [PATCH 12/12] qla2xxx: Add SLER and PI control support Nilesh Javali

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=202008190517.dxLmqIFK%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=njavali@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