diff options
| author | Suganath Prabu <suganath-prabu.subramani@broadcom.com> | 2018-10-31 18:53:35 +0530 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-02-12 19:46:58 +0100 |
| commit | 83430596d497eaf7ecb431dc6105e9299f4acf0a (patch) | |
| tree | 0f99bf0d58dfd6eeaef4cac79a185435bd917db8 /arch | |
| parent | 3d08cdeb448699cad9c6d82be41de7ccbc121add (diff) | |
| download | linux-stable-83430596d497eaf7ecb431dc6105e9299f4acf0a.tar.gz linux-stable-83430596d497eaf7ecb431dc6105e9299f4acf0a.tar.bz2 linux-stable-83430596d497eaf7ecb431dc6105e9299f4acf0a.zip | |
scsi: mpt3sas: Call sas_remove_host before removing the target devices
[ Upstream commit dc730212e8a378763cb182b889f90c8101331332 ]
Call sas_remove_host() before removing the target devices in the driver's
.remove() callback function(i.e. during driver unload time). So that
driver can provide a way to allow SYNC CACHE, START STOP unit commands
etc. (which are issued from SML) to the target drives during driver unload
time.
Once sas_remove_host() is called before removing the target drives then
driver can just clean up the resources allocated for target devices and no
need to call sas_port_delete_phy(), sas_port_delete() API's as these API's
internally called from sas_remove_host().
Signed-off-by: Suganath Prabu <suganath-prabu.subramani@broadcom.com>
Reviewed-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions