Re: [PATCH] scsi: ibmvscsi_tgt: Remove target_wait_for_sess_cmd()

2018-10-17 Thread Martin K. Petersen
Bryant, > There is currently a bug with the driver where there is never a call > to target_sess_cmd_list_set_waiting(), it only called > target_wait_for_sess_cmd(), which basically means that the > sess_wait_list would always be empty. > > Thus, list_empty(&sess->sess_wait_list) = true, (eg: no

Re: [PATCH] scsi: ibmvscsi_tgt: Remove target_wait_for_sess_cmd()

2018-10-17 Thread Mike Christie
On 10/16/2018 12:34 PM, Ly, Bryant wrote: > From: "Bryant G. Ly" > > There is currently a bug with the driver where there is never a > call to target_sess_cmd_list_set_waiting(), it only called > target_wait_for_sess_cmd(), which basically means that the > sess_wait_list would always be empty. >

[PATCH] scsi: ibmvscsi_tgt: Remove target_wait_for_sess_cmd()

2018-10-16 Thread Ly, Bryant
From: "Bryant G. Ly" There is currently a bug with the driver where there is never a call to target_sess_cmd_list_set_waiting(), it only called target_wait_for_sess_cmd(), which basically means that the sess_wait_list would always be empty. Thus, list_empty(&sess->sess_wait_list) = true, (eg: no