From: John Garry <john.garry@huawei.com>
To: <jejb@linux.vnet.ibm.com>, <martin.petersen@oracle.com>
Cc: <hare@suse.com>, <yanaijie@huawei.com>, <linuxarm@huawei.com>,
<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<joe@perches.com>, John Garry <john.garry@huawei.com>
Subject: [PATCH v2 5/5] scsi: libsas: Remove pcidev reference
Date: Thu, 15 Nov 2018 18:20:32 +0800 [thread overview]
Message-ID: <1542277232-135789-6-git-send-email-john.garry@huawei.com> (raw)
In-Reply-To: <1542277232-135789-1-git-send-email-john.garry@huawei.com>
Not all host drivers are PCI drivers - like hisi_sas, which supports a
platform driver - so remove reference to "pcidev".
Signed-off-by: John Garry <john.garry@huawei.com>
---
drivers/scsi/libsas/sas_discover.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/libsas/sas_discover.c b/drivers/scsi/libsas/sas_discover.c
index 3eb9ff2..726ada9 100644
--- a/drivers/scsi/libsas/sas_discover.c
+++ b/drivers/scsi/libsas/sas_discover.c
@@ -186,7 +186,7 @@ int sas_notify_lldd_dev_found(struct domain_device *dev)
res = i->dft->lldd_dev_found(dev);
if (res) {
- pr_warn("driver on pcidev %s cannot handle device %llx, error:%d\n",
+ pr_warn("driver on host %s cannot handle device %llx, error:%d\n",
dev_name(sas_ha->dev),
SAS_ADDR(dev->sas_addr), res);
}
--
1.9.1
next prev parent reply other threads:[~2018-11-15 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 10:20 [PATCH v2 0/5] libsas: Some logging tidy-up John Garry
2018-11-15 10:20 ` [PATCH v2 1/5] scsi: libsas: Delete sas_dump.{c, h} John Garry
2018-11-15 10:20 ` [PATCH v2 2/5] scsi: libsas: Use pr_fmt(fmt) John Garry
2018-11-15 10:20 ` [PATCH v2 3/5] scsi: libsas: Drop sas_printk() John Garry
2018-11-15 10:20 ` [PATCH v2 4/5] scsi: libsas: Drop SAS_DPRINTK() and revise logs levels John Garry
2018-11-15 10:20 ` John Garry [this message]
2018-11-15 12:34 ` [PATCH v2 0/5] libsas: Some logging tidy-up Joe Perches
2018-11-15 19:40 ` 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=1542277232-135789-6-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=yanaijie@huawei.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;
as well as URLs for NNTP newsgroup(s).