From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH linux-stable-rc] scsi: lpfc: lpfc_defer_pt2pt_acc can be static
Date: Mon, 23 Nov 2020 04:40:37 +0800 [thread overview]
Message-ID: <20201122204037.GA57892@33dc8734b97e> (raw)
In-Reply-To: <202011230453.MFgFSwpt-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
Fixes: 6b8fbd9b2db0 ("scsi: lpfc: Fix pt2pt discovery on SLI3 HBAs")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
lpfc_nportdisc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/lpfc/lpfc_nportdisc.c b/drivers/scsi/lpfc/lpfc_nportdisc.c
index 2a340624bfc99b..0bd7b2048ec065 100644
--- a/drivers/scsi/lpfc/lpfc_nportdisc.c
+++ b/drivers/scsi/lpfc/lpfc_nportdisc.c
@@ -286,7 +286,7 @@ lpfc_els_abort(struct lpfc_hba *phba, struct lpfc_nodelist *ndlp)
* This routine is only called if we are SLI3, direct connect pt2pt
* mode and the remote NPort issues the PLOGI after link up.
*/
-void
+static void
lpfc_defer_pt2pt_acc(struct lpfc_hba *phba, LPFC_MBOXQ_t *link_mbox)
{
LPFC_MBOXQ_t *login_mbox;
next prev parent reply other threads:[~2020-11-22 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 20:40 [linux-stable-rc:linux-5.4.y 1860/3341] drivers/scsi/lpfc/lpfc_nportdisc.c:290:1: sparse: sparse: symbol 'lpfc_defer_pt2pt_acc' was not declared. Should it be kernel test robot
2020-11-22 20:40 ` kernel test robot [this message]
2020-11-24 14:37 ` [RFC PATCH linux-stable-rc] scsi: lpfc: lpfc_defer_pt2pt_acc can be static James Smart
2020-11-24 17:08 ` Greg Kroah-Hartman
2020-11-24 23:15 ` Philip Li
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=20201122204037.GA57892@33dc8734b97e \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.