Re: [PATCH RESEND] scsi_transport_sas: move bsg destructor into sas_rphy_remove

2014-05-02 Thread Joe Lawrence
On Wed, 2 Apr 2014 16:48:52 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: On Wed, 2 Apr 2014 16:40:41 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: Since bsg creation is a side effect of sas_rphy_add, move its complementary removal call into sas_rphy_remove. Hello James,

Re: [PATCH RESEND] scsi_transport_sas: move bsg destructor into sas_rphy_remove

2014-05-02 Thread Dan Williams
On Fri, May 2, 2014 at 12:01 PM, Joe Lawrence joe.lawre...@stratus.com wrote: On Wed, 2 Apr 2014 16:48:52 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: On Wed, 2 Apr 2014 16:40:41 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: Since bsg creation is a side effect of sas_rphy_add,

Re: [PATCH RESEND] scsi_transport_sas: move bsg destructor into sas_rphy_remove

2014-04-02 Thread Joe Lawrence
On Wed, 2 Apr 2014 16:40:41 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: Since bsg creation is a side effect of sas_rphy_add, move its complementary removal call into sas_rphy_remove. Hello James, This a resend of a patch posted to quiet an end-device sysfs warning in its device

[PATCH RESEND] scsi_transport_sas: move bsg destructor into sas_rphy_remove

2014-04-02 Thread Joe Lawrence
The recent change in sysfs, bcdde7e221a8750f9b62b6d0bd31b72ea4ad9309 sysfs: make __sysfs_remove_dir() recursive revealed an asymmetric rphy device creation/deletion sequence in scsi_transport_sas: modprobe mpt2sas sas_rphy_add device_add A rphy-dev device_add B