linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Nilesh Javali <njavali@marvell.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: [linux-next:master 12741/13109] drivers/scsi/qla2xxx/qla_nvme.c:1183:20: warning: unused variable 'fcport'
Date: Tue, 29 Aug 2023 08:28:58 +0800	[thread overview]
Message-ID: <202308290833.sKkoSSeO-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   2ee82481c392eec06a7ef28df61b7f0d8e45be2e
commit: 27177862de9676c8c35b86bf89c38864fbe5ed71 [12741/13109] scsi: qla2xxx: Fix nvme_fc_rcv_ls_req() undefined error
config: microblaze-randconfig-r024-20230829 (https://download.01.org/0day-ci/archive/20230829/202308290833.sKkoSSeO-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230829/202308290833.sKkoSSeO-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/202308290833.sKkoSSeO-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/scsi/qla2xxx/qla_nvme.c: In function 'qla2xxx_process_purls_pkt':
>> drivers/scsi/qla2xxx/qla_nvme.c:1183:20: warning: unused variable 'fcport' [-Wunused-variable]
    1183 |         fc_port_t *fcport = uctx->fcport;
         |                    ^~~~~~


vim +/fcport +1183 drivers/scsi/qla2xxx/qla_nvme.c

875386b9885782 Manish Rangankar 2023-08-21  1167  
875386b9885782 Manish Rangankar 2023-08-21  1168  /*
875386b9885782 Manish Rangankar 2023-08-21  1169   * qla2xxx_process_purls_pkt() - Pass-up Unsolicited
875386b9885782 Manish Rangankar 2023-08-21  1170   * Received FC-NVMe Link Service pkt to nvme_fc_rcv_ls_req().
875386b9885782 Manish Rangankar 2023-08-21  1171   * LLDD need to provide memory for response buffer, which
875386b9885782 Manish Rangankar 2023-08-21  1172   * will be used to reference the exchange corresponding
875386b9885782 Manish Rangankar 2023-08-21  1173   * to the LS when issuing an ls response. LLDD will have to free
875386b9885782 Manish Rangankar 2023-08-21  1174   * response buffer in lport->ops->xmt_ls_rsp().
875386b9885782 Manish Rangankar 2023-08-21  1175   *
875386b9885782 Manish Rangankar 2023-08-21  1176   * @vha: SCSI qla host
875386b9885782 Manish Rangankar 2023-08-21  1177   * @item: ptr to purex_item
875386b9885782 Manish Rangankar 2023-08-21  1178   */
875386b9885782 Manish Rangankar 2023-08-21  1179  static void
875386b9885782 Manish Rangankar 2023-08-21  1180  qla2xxx_process_purls_pkt(struct scsi_qla_host *vha, struct purex_item *item)
875386b9885782 Manish Rangankar 2023-08-21  1181  {
875386b9885782 Manish Rangankar 2023-08-21  1182  	struct qla_nvme_unsol_ctx *uctx = item->purls_context;
875386b9885782 Manish Rangankar 2023-08-21 @1183  	fc_port_t *fcport = uctx->fcport;
875386b9885782 Manish Rangankar 2023-08-21  1184  	struct qla_nvme_lsrjt_pt_arg a;
27177862de9676 Nilesh Javali    2023-08-24  1185  	int ret = 1;
875386b9885782 Manish Rangankar 2023-08-21  1186  

:::::: The code at line 1183 was first introduced by commit
:::::: 875386b98857822b77ac7f95bdf367b70af5b78c scsi: qla2xxx: Add Unsolicited LS Request and Response Support for NVMe

:::::: TO: Manish Rangankar <mrangankar@marvell.com>
:::::: CC: Martin K. Petersen <martin.petersen@oracle.com>

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


                 reply	other threads:[~2023-08-29  0:29 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=202308290833.sKkoSSeO-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=martin.petersen@oracle.com \
    --cc=njavali@marvell.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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