From: kernel test robot <lkp@intel.com>
To: Deepak Ukey <deepak.ukey@microchip.com>, linux-scsi@vger.kernel.org
Cc: kbuild-all@lists.01.org,
Vasanthalakshmi.Tharmarajan@microchip.com,
Viswas.G@microchip.com, deepak.ukey@microchip.com,
jinpu.wang@profitbricks.com, martin.petersen@oracle.com,
dpf@google.com, yuuzheng@google.com, auradkar@google.com,
vishakhavc@google.com
Subject: [RFC PATCH] pm80xx : pm8001_queue_phyup() can be static
Date: Thu, 25 Jun 2020 19:59:48 +0800 [thread overview]
Message-ID: <20200625115948.GA63645@9d911e2d61d0> (raw)
In-Reply-To: <20200624120322.6265-3-deepak.ukey@microchip.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
pm80xx_hwi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/pm8001/pm80xx_hwi.c b/drivers/scsi/pm8001/pm80xx_hwi.c
index 748c7a06262fb..80e992d9ea314 100644
--- a/drivers/scsi/pm8001/pm80xx_hwi.c
+++ b/drivers/scsi/pm8001/pm80xx_hwi.c
@@ -49,7 +49,7 @@
static int pm80xx_chip_phy_ctl_req(struct pm8001_hba_info *pm8001_ha,
u32 phyId, u32 phy_op);
-void pm8001_queue_phyup(struct pm8001_hba_info *pm8001_ha, int phy_id)
+static void pm8001_queue_phyup(struct pm8001_hba_info *pm8001_ha, int phy_id)
{
int i;
next prev parent reply other threads:[~2020-06-25 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 12:03 [PATCH V2 0/3] pm80xx : Updates for the driver version 0.1.39 Deepak Ukey
2020-06-24 12:03 ` [PATCH V2 1/3] pm80xx : Support for get phy profile functionality Deepak Ukey
2020-06-24 14:18 ` kernel test robot
2020-06-24 15:40 ` kernel test robot
2020-06-25 10:40 ` [RFC PATCH] pm80xx : pm8001_chip_get_phy_profile() can be static kernel test robot
2020-06-24 12:03 ` [PATCH V2 2/3] pm80xx : Staggered spin up support Deepak Ukey
2020-06-24 15:28 ` kernel test robot
2020-06-24 17:33 ` kernel test robot
2020-06-25 11:59 ` kernel test robot [this message]
2020-06-24 12:03 ` [PATCH V2 3/3] pm80xx : Wait for PHY startup before draining libsas queue Deepak Ukey
2020-06-24 17:06 ` John Garry
2020-07-14 4:49 ` Deepak.Ukey
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=20200625115948.GA63645@9d911e2d61d0 \
--to=lkp@intel.com \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=auradkar@google.com \
--cc=deepak.ukey@microchip.com \
--cc=dpf@google.com \
--cc=jinpu.wang@profitbricks.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vishakhavc@google.com \
--cc=yuuzheng@google.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