This upgrades the Fusion-MPT driver from 2.03.00.02 to 2.03.01.01.

Bug Fixes:
 o Added back missing queuecommand entry point define ?!
 o Added to code to break marriage of two controllers during unload
  (could cause a panic)
 o SCSI driver will de-register with base driver if no SCSI-capable
   adapters found

Minor Changes:
 o Removed errant spaces at ends of lines  (most of the changes)
 o Moved code around (and in-lined) some functions for performance reasons.
 o Modified /proc functionality to facilitate testing with 2.5
 o Added a call to synchronize_irq on unload (HP request)
 o Modified load of base to close a potential hole
 o Added code to set the FW IO coalescing depth (IBM request)
 o Changed return when mptctl driver registration fails (Kernel.org request)
 o SCSI driver detect routine calls a generic spinlock for all kernels
   (Kernel.org request)
 o Controller RAID page dynamic instead of static

Currently running a multi-disk stress test w/ 2.5.53,  this patch and driver
built-in. Verified basic reset handling is working properly.

Showing the logo on every open became annoying. I leave it up to the driver writers when they want to display the logo. Fo embeded devices it probably is wise to have them set there mode themselves then display the logo to let them know if the hartdware worked. FOnt header file location changed.

on the end of __GNUC_MINOR"

James Bottomley confirmed the "deprecated" attribute requires gcc 3.1
and onward, not gcc 3.0.

This updates the check in compiler.h accordingly.

into home.transmeta.com:/home/torvalds/v2.5/linux

into home.transmeta.com:/home/torvalds/v2.5/linux

into home.transmeta.com:/home/torvalds/v2.5/linux

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

into home.transmeta.com:/home/torvalds/v2.5/linux

into tetrachloride.(none):/mnt/stuff/kernel/2.5/warnings

Atari NCR5380 SCSI driver tag bitmap updates:
  - Use DECLARE_BITMAP() to declare the tag bitmap
  - Remove `MAX_TAGS must be a multiple of 32', which is no longer true
  - Declare and use CLEAR_BITMAP() to set all bits in a bitmap to zero
  - Fix bitops call problems that got unnoticed before

into tp1.ruhr-uni-bochum.de:/scratch/kai/linux-2.5.make

Now that we have a unique suffix for kernel modules (.ko), we
can extend to former "make some/object.o" to work for kernel modules
as well, even composite ones.

It's as easy as "make some/dir/module.ko".

(Sam Ravnborg/me)

Moved archhelp to arch/x86_64/Makefile
Introduced usage of $(build) and $(clean)
Use kbuild clean infrastructure

Moved archhelp to arch/sparc64/Makefile
introduced usage of $(build)
Removed superflous targets archclean and archmrproper

Moved archhelp to arch/arm/Makefile
Introduced usage of $(build) and $(clean)

arch/$(ARCH)/Makefile already contains the kbuild required additions
to allow the kernel to be built for the architecture in question.
Moving archhelp centralise this information, and no longer require a
boot directory to exist to utilise this feature.
  
Update i386 to define archhelp in arch/$(ARCH)/Makefile
Other architectures will be updated in next cset.

The former macro $(descend ...) hide for make the fact that a recursively make was
invoked. The replacement $(Q)$(MAKE) -f scripts/Makefile.build obj=dir was too verbose.
  
Introduced $(build) and $(clean) allowing the following syntax:
$(Q)$(MAKE) $(build)=arch/i386/boot target
and similar for clean.
  
Introduced $(build) and $(clean) in general, and for i386 architecture.

Add $(srctree)/ etc. to some more places where it was still missing.

into are.twiddle.net:/home/rth/BK/tga-2.5

Speeds up rendering of text by around 7x for 8bpp cards,
as you'd expect from the difference in the volume of data
passed across the bus.  Thus the win should be about 31x
for 32bpp cards.

The generated .tmp_kallsyms.S needs to use .long / .quad for
32/64 bit archs. To know which arch we're compiling for, we
use the preprocessor and BITS_PER_LONG from <asm/types.h>.

Unfortunately, asm/types.h was not safe to include from assembler
files, so lots of #ifndef __ASSEMBLY__ needed to be added - should
be fine now, untested for != i386, though.

into home.transmeta.com:/home/torvalds/v2.5/linux

but somehow are not handled by the DV state machine.  This ensures that
the behavior seen before DV is restored in the event of a DV state machine
failure.

but is still required in earlier kernels.

on some tape and cdrom devices.