diff options
| author | Jason Yan <yanaijie@huawei.com> | 2018-09-25 05:56:52 +0300 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2018-09-26 04:20:23 +0300 |
| commit | 32c850bf587f993b2620b91e5af8a64a7813f504 (patch) | |
| tree | bf3166004098e7a1b5945a1acefc7d6ce815dad5 /drivers/scsi/libsas/sas_ata.c | |
| parent | 640208a1c91c380a09056a26d3750b137b7e8c4d (diff) | |
| download | linux-32c850bf587f993b2620b91e5af8a64a7813f504.tar.xz | |
scsi: libsas: always unregister the old device if going to discover new
If we went into sas_rediscover_dev() the attached_sas_addr was already insured
not to be zero. So it's unnecessary to check if the attached_sas_addr is zero.
And although if the sas address is not changed, we always have to unregister
the old device when we are going to register a new one. We cannot just leave
the device there and bring up the new.
Signed-off-by: Jason Yan <yanaijie@huawei.com>
CC: chenxiang <chenxiang66@hisilicon.com>
CC: John Garry <john.garry@huawei.com>
CC: Johannes Thumshirn <jthumshirn@suse.de>
CC: Ewan Milne <emilne@redhat.com>
CC: Christoph Hellwig <hch@lst.de>
CC: Tomas Henzl <thenzl@redhat.com>
CC: Dan Williams <dan.j.williams@intel.com>
CC: Hannes Reinecke <hare@suse.com>
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/scsi/libsas/sas_ata.c')
0 files changed, 0 insertions, 0 deletions