1. 18 Oct, 2004 10 commits
  2. 19 Oct, 2004 1 commit
  3. 18 Oct, 2004 9 commits
  4. 17 Oct, 2004 6 commits
  5. 16 Oct, 2004 7 commits
  6. 15 Oct, 2004 7 commits
    • Linus Torvalds's avatar
      Linux 2.6.9-final · 788c16bd
      Linus Torvalds authored
      Let's try the 2.4.x release methodology
      788c16bd
    • Alexander Viro's avatar
      [PATCH] typhoon.c missing include · 04f29e41
      Alexander Viro authored
      DMA_32BIT_MASK is declared in linux/dma-mapping.h; not all platforms get
      it from already included headers, so we need explicit include here (fixes
      breakage at least on alpha and sparc64).
      Signed-off-by: default avatarAl Viro <viro@parcelfarce.linux.theplanet.co.uk>
      04f29e41
    • Alan Stern's avatar
      [PATCH] Let LLD specify INQUIRY length · 6928192f
      Alan Stern authored
      That sounds like a good suggestion.  Even better, instead of adding a new
      field we can simply use the existing inquiry_length.
      
      This patch changes scsi_probe_lun() to use the value in
      sdev->inquiry_length for the first INQUIRY attempt, if that value is
      nonzero.  Subsequent attempts are based, as before, on the blacklist flags
      and the Additional Length field in the INQUIRY data.
      
      The patch also contains a fairly extensive reorganization of the
      subroutine.  All the code that was duplicated for sending the INQUIRY
      command twice has been consolidated.  The routine now makes up to three
      passes:
      
      	In the first pass, the transfer length is the value initially
      	found in sdev->inquiry_length if that has been set, otherwise
      	it is the current conservative 36 bytes.
      
      	If the first pass succeeds, the routine retrieves the blist flags
      	for the device and checks the Additional Length field.  The blist
      	flags take precedence over sdev->inquiry_length, which in turn
      	takes precedence over the Additional Length.  If it turns out
      	there is more data available than we transferred the first time,
      	a second pass tries to get it.
      
      	If the second pass succeeds the INQUIRY data may have changed,
      	so the blist flags are looked up again and the Additional Length
      	is checked again.  If not, a third pass tries to get the data
      	back, using the same transfer length as the first pass.
      
      Finally, the value stored in sdev->inquiry_length is set to the amount
      actually transferred or the size computed from the Additional Length,
      whichever is smaller.
      
      Although the net change in the source file size is small, the new routine
      has more comments and less code.  Overall I think it's an improvement.
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      6928192f
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/gregkh/linux/fix-2.6 · afc028ba
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.6/linux
      afc028ba
    • James Bottomley's avatar
      Merge titanic.il.steeleye.com:/home/jejb/BK/scsi-misc-2.6 · d74833b6
      James Bottomley authored
      into titanic.il.steeleye.com:/home/jejb/BK/scsi-target-2.6
      d74833b6
    • John Rose's avatar
      [PATCH] PCI Hotplug: rpaphp safe list traversal · b86da52f
      John Rose authored
      Hoping you will accept this fix.  The bug can cause a crash upon hotplug
      remove.  The bug involves unsafe traversal of a list while deleting list
      members.  The fix uses list_for_each_safe() rather than
      list_for_each().  Also threw in an initialization to get rid of a
      compiler warning.
      Signed-off-by: default avatarJohn Rose <johnrose@austin.ibm.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      b86da52f
    • James Bottomley's avatar
      SCSI: Fix problems with non-power-of-two sector size discs · c7014083
      James Bottomley authored
      We can't support them, but the system should disable them cleanly
      and continue when they're detected (at the moment it
      dumps a stack trace).
      
      The fix (hack) is to set them to zero size and 512 byte
      sectors.  This means they're still amenable to ioctls (like
      to reformat them with a useful block size) but cannot
      be read from or written to.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      c7014083