From: kernel test robot <lkp@intel.com>
To: James Smart <jsmart2021@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>, Paul Ely <paul.ely@broadcom.com>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>
Subject: drivers/scsi/lpfc/lpfc_nvme.c:879:19: warning: variable 'phba' set but not used
Date: Wed, 4 Nov 2020 14:48:02 +0800 [thread overview]
Message-ID: <202011041457.M7loh86s-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2629 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4ef8451b332662d004df269d4cdeb7d9f31419b5
commit: e96a22b0b7c252295180c12128af380282e3b8c5 lpfc: Refactor Send LS Abort support
date: 6 months ago
config: x86_64-customedconfig-lck8195-cfld1 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e96a22b0b7c252295180c12128af380282e3b8c5
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout e96a22b0b7c252295180c12128af380282e3b8c5
# 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 warnings (new ones prefixed by >>):
drivers/scsi/lpfc/lpfc_nvme.c: In function 'lpfc_nvme_ls_abort':
>> drivers/scsi/lpfc/lpfc_nvme.c:879:19: warning: variable 'phba' set but not used [-Wunused-but-set-variable]
879 | struct lpfc_hba *phba;
| ^~~~
vim +/phba +879 drivers/scsi/lpfc/lpfc_nvme.c
862
863 /**
864 * lpfc_nvme_ls_abort - Abort a prior NVME LS request
865 * @lpfc_nvme_lport: Transport localport that LS is to be issued from.
866 * @lpfc_nvme_rport: Transport remoteport that LS is to be sent to.
867 * @pnvme_lsreq - the transport nvme_ls_req structure for the LS
868 *
869 * Driver registers this routine to abort a NVME LS request that is
870 * in progress (from the transports perspective).
871 **/
872 static void
873 lpfc_nvme_ls_abort(struct nvme_fc_local_port *pnvme_lport,
874 struct nvme_fc_remote_port *pnvme_rport,
875 struct nvmefc_ls_req *pnvme_lsreq)
876 {
877 struct lpfc_nvme_lport *lport;
878 struct lpfc_vport *vport;
> 879 struct lpfc_hba *phba;
880 struct lpfc_nodelist *ndlp;
881 int ret;
882
883 lport = (struct lpfc_nvme_lport *)pnvme_lport->private;
884 if (unlikely(!lport))
885 return;
886 vport = lport->vport;
887 phba = vport->phba;
888
889 if (vport->load_flag & FC_UNLOADING)
890 return;
891
892 ndlp = lpfc_findnode_did(vport, pnvme_rport->port_id);
893
894 ret = __lpfc_nvme_ls_abort(vport, ndlp, pnvme_lsreq);
895 if (!ret)
896 atomic_inc(&lport->xmt_ls_abort);
897 }
898
---
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: 51221 bytes --]
reply other threads:[~2020-11-04 6:48 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=202011041457.M7loh86s-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jsmart2021@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.ely@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
all inboxes | Powered by JetHome®