1. 10 3月, 2006 1 次提交
    • A
      [SCSI] zfcp: fix device registration issues · ad58f7db
      Andreas Herrmann 提交于
      The patch fixes following issues:
      
      (1) Replace scsi_add_device with scsi_scan_target.
      (Thus the rport instead of the scsi_host becomes parent of a
      scsi_target again.)
      
      (2) Avoid scsi_device allocation during registration of an remote port.
      (Would be done during fc_scsi_scan_rport.)
      
      (3) Fix queuecommand behaviour when an zfcp unit is blocked.
      (Call scsi_done with DID_NO_CONNECT instead of returning
      SCSI_MLQUEUE_DEVICE_BUSY otherwise we might end up waiting
      for completion in blk_execute_rq for ever.)
      Signed-off-by: NAndreas Herrmann <aherrman@de.ibm.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      ad58f7db
  2. 03 3月, 2006 1 次提交
  3. 13 2月, 2006 1 次提交
  4. 02 2月, 2006 1 次提交
  5. 15 1月, 2006 2 次提交
  6. 02 12月, 2005 1 次提交
  7. 20 9月, 2005 5 次提交
  8. 28 8月, 2005 1 次提交
  9. 21 6月, 2005 1 次提交
  10. 18 6月, 2005 4 次提交
  11. 14 6月, 2005 1 次提交
    • A
      [SCSI] zfcp: fix bug during adapter shutdown · 1db2c9c0
      Andreas Herrmann 提交于
      Fixes a race between zfcp_fsf_req_dismiss_all and
      zfcp_qdio_reqid_check. During adapter shutdown it occurred that a
      request was cleaned up twice. First during its normal
      completion. Second when dismiss_all was called.  The fix is to
      serialize access to fsf request list between zfcp_fsf_req_dismiss_all
      and zfcp_qdio_reqid_check and delete a fsf request from the list if
      its completion is triggered.  (Additionally a rwlock was replaced by a
      spinlock and fsf_req_cleanup was eliminated.)
      Signed-off-by: NAndreas Herrmann <aherrman@de.ibm.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      1db2c9c0
  12. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4