> (v2: Make access of qla_tgt_sess->sess_cmd_lock use normal spin_lock_irq() > access as qla_hw_data->hardware_lock is already disabling interrupts) Do you have a tree where the end result of this is applied? I'm just curious if there's anywhere that sess_cmd_lock is taken outside of hardware_lock. If not then we don't even need that extra lock. Assuming I merged everything correctly, in my tree sess_cmd_lock looks like it is never taken outside of hardware_lock. So we can just get rid of the superfluous lock. - R. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
