From: kbuild test robot <lkp@intel.com>
To: balsundar.p@microsemi.com
Cc: kbuild-all@lists.01.org, linux-scsi@vger.kernel.org,
jejb@linux.vnet.ibm.com, aacraid@microsemi.com
Subject: [RFC PATCH] scsi: aacraid: aac_schedule_bus_scan() can be static
Date: Wed, 16 Oct 2019 02:58:07 +0800 [thread overview]
Message-ID: <20191015185807.gkfkf44bc7accjua@332d0cec05f4> (raw)
In-Reply-To: <1571120524-6037-7-git-send-email-balsundar.p@microsemi.com>
Fixes: ffcdda7d81b4 ("scsi: aacraid: send AIF request post IOP RESET")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
commsup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/aacraid/commsup.c b/drivers/scsi/aacraid/commsup.c
index 1c3beea2b3c57..5a8a999606ea3 100644
--- a/drivers/scsi/aacraid/commsup.c
+++ b/drivers/scsi/aacraid/commsup.c
@@ -1464,7 +1464,7 @@ static void aac_handle_aif(struct aac_dev * dev, struct fib * fibptr)
}
}
-void aac_schedule_bus_scan(struct aac_dev *aac)
+static void aac_schedule_bus_scan(struct aac_dev *aac)
{
if (aac->sa_firmware)
aac_schedule_safw_scan_worker(aac);
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] scsi: aacraid: aac_schedule_bus_scan() can be static
Date: Wed, 16 Oct 2019 02:58:07 +0800 [thread overview]
Message-ID: <20191015185807.gkfkf44bc7accjua@332d0cec05f4> (raw)
In-Reply-To: <1571120524-6037-7-git-send-email-balsundar.p@microsemi.com>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Fixes: ffcdda7d81b4 ("scsi: aacraid: send AIF request post IOP RESET")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
commsup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/aacraid/commsup.c b/drivers/scsi/aacraid/commsup.c
index 1c3beea2b3c57..5a8a999606ea3 100644
--- a/drivers/scsi/aacraid/commsup.c
+++ b/drivers/scsi/aacraid/commsup.c
@@ -1464,7 +1464,7 @@ static void aac_handle_aif(struct aac_dev * dev, struct fib * fibptr)
}
}
-void aac_schedule_bus_scan(struct aac_dev *aac)
+static void aac_schedule_bus_scan(struct aac_dev *aac)
{
if (aac->sa_firmware)
aac_schedule_safw_scan_worker(aac);
next prev parent reply other threads:[~2019-10-15 18:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 6:21 [PATCH 0/7] scsi: aacraid updates balsundar.p
2019-10-15 6:21 ` [PATCH 1/7] scsi: aacraid: fix illegal IO beyond last LBA balsundar.p
2019-10-15 6:21 ` [PATCH 2/7] scsi: aacraid: fixed IO reporting error balsundar.p
2019-10-15 6:22 ` [PATCH 3/7] scsi: aacraid: fixed firmware assert issue balsundar.p
2019-10-15 6:22 ` [PATCH 4/7] scsi: aacraid: setting different timeout for src and thor balsundar.p
2019-10-15 6:22 ` [PATCH 5/7] scsi: aacraid: check adapter health balsundar.p
2019-10-15 6:22 ` [PATCH 6/7] scsi: aacraid: send AIF request post IOP RESET balsundar.p
2019-10-15 18:58 ` kbuild test robot
2019-10-15 18:58 ` kbuild test robot
2019-10-15 18:58 ` kbuild test robot [this message]
2019-10-15 18:58 ` [RFC PATCH] scsi: aacraid: aac_schedule_bus_scan() can be static kbuild test robot
2019-10-18 7:26 ` Balsundar.P
2019-10-18 7:26 ` Balsundar.P
2019-10-15 6:22 ` [PATCH 7/7] scsi: aacraid: bump version balsundar.p
2019-10-18 23:35 ` [PATCH 0/7] scsi: aacraid updates Martin K. Petersen
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=20191015185807.gkfkf44bc7accjua@332d0cec05f4 \
--to=lkp@intel.com \
--cc=aacraid@microsemi.com \
--cc=balsundar.p@microsemi.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-scsi@vger.kernel.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.