summaryrefslogtreecommitdiffstats
path: root/include/scsi/libsas.h
diff options
context:
space:
mode:
authorJohn Garry <john.garry@huawei.com>2019-04-12 16:57:54 +0800
committerMartin K. Petersen <martin.petersen@oracle.com>2019-04-15 18:55:00 -0400
commita5b38d3159eac6a30c1c57d67707c141b9ac3efb (patch)
tree71fc162fe1d99af616c3b7644bfc48464b5178cb /include/scsi/libsas.h
parentf7ddb43eed7bcb096852defb4f57b38393339695 (diff)
downloadlinux-a5b38d3159eac6a30c1c57d67707c141b9ac3efb.tar.gz
linux-a5b38d3159eac6a30c1c57d67707c141b9ac3efb.tar.bz2
linux-a5b38d3159eac6a30c1c57d67707c141b9ac3efb.zip
scsi: libsas: Improve vague log in SAS rediscovery
When an expander PHY which was part of a wideport disconnects, we would see a log like this from sas_rediscover(): [ 39.695554] sas: phy20 part of wide port with phy16 Here, phy20 is the PHY that disconnected, and phy16 is the lowest indexed member PHY of the wideport. The log implies the phy20 is still part of the wideport with phy16, so is misleading or, at least, vague. Improve the logs in SAS rediscovery by removing this log and adding a log in sas_rediscover_dev() to tell what's really going on. While we're at it, also make the logs in sas_find_bcast_dev() more informative (and more consistent with the reset of the expander logs). Signed-off-by: John Garry <john.garry@huawei.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'include/scsi/libsas.h')
0 files changed, 0 insertions, 0 deletions