Re: [PATCH 1/3] SCSI: Introduce device_lock and target_lock in Scsi_Host

2015-10-14 Thread kbuild test robot
Hi Johannes, [auto build test ERROR on scsi/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base] url: https://github.com/0day-ci/linux/commits/Johannes-Thumshirn/SCSI-Introduce-device_lock-and-target_lock-in-Scsi_Host/20151014-215532 config:

Re: [PATCH 1/3] SCSI: Introduce device_lock and target_lock in Scsi_Host

2015-10-14 Thread Hannes Reinecke
On 10/14/2015 03:50 PM, Johannes Thumshirn wrote: > Introduce target_lock and device_lock to untangle the __devices and __targets > lists from the host_lock. > > Signed-off-by: Johannes Thumshirn > --- Actually, you need to convert scsi_lookup_by_target, too. That, too,

[PATCH 1/3] SCSI: Introduce device_lock and target_lock in Scsi_Host

2015-10-14 Thread Johannes Thumshirn
Introduce target_lock and device_lock to untangle the __devices and __targets lists from the host_lock. Signed-off-by: Johannes Thumshirn --- drivers/scsi/53c700.c | 3 +++ drivers/scsi/hosts.c | 2 ++ drivers/scsi/scsi.c | 8

Re: [PATCH 1/3] SCSI: Introduce device_lock and target_lock in Scsi_Host

2015-10-14 Thread Hannes Reinecke
On 10/14/2015 03:50 PM, Johannes Thumshirn wrote: > Introduce target_lock and device_lock to untangle the __devices and __targets > lists from the host_lock. > > Signed-off-by: Johannes Thumshirn > --- > drivers/scsi/53c700.c | 3 +++ > drivers/scsi/hosts.c | 2 ++