1. 16 Aug, 2003 7 commits
    • David Jeffery's avatar
      [PATCH] ips 4/4: version resync · b768d5c4
      David Jeffery authored
      This patch has no code changes.  It is just a resync of all the version
      numbers with the 6.10 driver and bumping up the driver version number.
      b768d5c4
    • James Bottomley's avatar
      ips 3/4: use pci_dma APIs and remove GFP abuse · cae1550d
      James Bottomley authored
      From: David Jeffery <david_jeffery@adaptec.com>
      (with minor reject fixes)
      
      This patch removes several places where we were using kmalloc flag
      tricks to always get memory <4GB instead of using the proper
      dma_alloc_consistent() API.  It also no longer #errors on when compiled
      for x86-64 kernels.
      cae1550d
    • James Bottomley's avatar
      ips 2/4: 2.4 resync · 23efa200
      James Bottomley authored
      From: David Jeffery <david_jeffery@adaptec.com>
      (with minor fixes for rejects)
      
      This patch is a resync with the 6.10 driver for 2.4 and updates the 2.4
      compatability code.  It adds a new wrapper function for differences
      between the 2.4 and 2.6 scsi proc interface,  forces pci posting in 3
      places, corrects using a meaningless constant of 0x80 to 0, and syncs
      comments that had changed. 
      23efa200
    • James Bottomley's avatar
      ips 1/4: lindent ips.c · 3ecd3030
      James Bottomley authored
      From: 	David Jeffery <david_jeffery@adaptec.com>
      (with fix ups for rejections on CONFIG_HIGHIO)
      
      This patch has no code changes.  It is only the result of running
      scripts/Lindent on drivers/scsi/ips.c in test3.  Rather than use this
      patch, it may be advisable to just run 
      
      sh scripts/Lindent drivers/scsi/ips.c 
      
      The nasty 3-4 space indenting in ips.c has always made it a pain to
      read.  The remaining patches in this patch set all assume ips.c has been
      lindented. 
      3ecd3030
    • Anton Blanchard's avatar
      [PATCH] another fix to sym2 hotplug conversion · 4e9f2a9a
      Anton Blanchard authored
      In sym_attach we call sym_hcb_attach. If it fails we call
      sym_free_resources which will call sym_hcb_free. Unfortunately
      sym_hcb_attach also calls sym_hcb_free on failure.
      
      This results in a bunch of things being freed twice and it looks like
      the sym2 memory allocator adds them to the freelist twice. Sometime later
      on we allocate the memory twice, with weird consequences.
      4e9f2a9a
    • Anton Blanchard's avatar
      [PATCH] minor fix to sym2 hotplug conversion · 1aac244b
      Anton Blanchard authored
      One problem we found when we hit a bad adapter, we need to use scsi_host_put.
      1aac244b
    • James Bottomley's avatar
      Add fastfail to SCSI · 5a659463
      James Bottomley authored
      This is the preliminary version with no error indications or
      control over the types of failures.
      5a659463
  2. 15 Aug, 2003 1 commit
    • James Bottomley's avatar
      oops in sd_shutdown · 177342da
      James Bottomley authored
      From: Andries Brouwer <aebr@win.tue.nl>
      
      I see an Oops in the SCSI code, caused by the fact that sdkp is NULL
      in sd_shutdown. "How can that be?", you will ask - dev->driver_data was set
      in sd_probe. But in my case sd_probe never finished. An insmod usb-storage
      hangs forever, or at least for more than six hours, giving ample opportunity
      to observe this race between sd_probe and sd_shutdown.
      (Of course sd_probe hangs in sd_revalidate disk.)
      
      Perhaps the obvious test is a good idea.
      Locking seems meaningless - sd_probe will never finish.
      177342da
  3. 14 Aug, 2003 27 commits
  4. 13 Aug, 2003 5 commits