Update SCSI drivers for the new IRQ API.  Also fix warnings and compilation
errors as encountered.

James Bottomley, please apply this patch.  It was sent out on
linux-scsi last week and drew no responses.

This is a patch for the scsi/gdth driver.  It was originally
done in 2.5.67, but the patch applies to 2.5.68.

There are two components to this patch.  The first component fixes
with compilation warnings (which did uncover real bugs).  The other component
(by Randy Dunlap) reduces stack size usage in gdth_ioctl().

The compilation warnings occur only when CONFIG_HIGHMEM=y in the kernel
configuration file (enable either 4gig or 64gig memory support).  This
changes the size of the dma_addr_t from u32 to u64.
The calls to pci_alloc_consistent return a value of type dma_addr_t.
But the code was casting a pointer to what was ony a 32-bit memory location.

This seonc component of the patch reduces stack size in
scsi/gdth.c::gdth_ioctl() by making each separate ioctl have its own
handler function, so that several large data structs are all declared on
the stack at the same time.

patch_name:     gdth-stack_warnings.patch
patch_version:  2003-04-14.16:31:30
author:         Randy.Dunlap <rddunlap@osdl.org>, Dave.Olien<dmo@osdl.org)
description:    reduce stack usage in drivers/scsi/gdth.c::gdth_ioctl()
                from 0xb50 to 0x5c (on P4, gcc 2.96); the large (ioctl)
                function sizes in gdth.o now are:
                        150 ioc_event
                        178 ioc_resetdrv
                        190 ioc_general
                        30c ioc_hdrlist
                        324 ioc_rescan
                so the largest cumulative size of calling gdth_ioctl() +
                a specific ioctl is 0x5c + 0x324 = 0x380.
		Fix compilation warnings in calls to pci_alloc_consistent()
		that occur only when CONFIG_HIGHMEM=y.  The compiler
		warnings result from dma_addr_t changing in size from u32
		to u64.
product:        Linux
product_versions: 2.5.67
changelog:      make each ioctl that uses large stack space into its own
                function;
                mostly moving lines of code around;
                duplicates some local data in multiple functions;
		fix compiler warnings by adding intermediate dma_addr_t local
		variables to hold returns from pci_alloc_consistent.
maintainer:     Achim Leubner (achim.leubner@intel.com)
diffstat:	=
 drivers/scsi/gdth.c      |  664 ++++++++++++++++++++++++++---------------------
 drivers/scsi/gdth_proc.c |    5
 2 files changed, 374 insertions(+), 295 deletions(-)

FYI:  The killer data structs in gdth_ioctl() (on x86, P4, gcc 2.96) are:
                sizeof gdth_cmd_str: 336 bytes
                sizeof gdth_ioctl_general: 356 bytes
                sizeof gdth_ioctl_event: 308 bytes
                sizeof gdth_ioctl_lockdrv: 204 bytes
                sizeof gdth_ioctl_rescan: 406 bytes

###

James -

The new printk for BLIST_INQUIRY_36 is getting a warning, and the
repeat_inquiry code is not quite right, since we reset *bflags after
getting the first INQUIRY.

Get rid of the warning, change the or-ing of the bflags settings, and get
rid of an extraneous BUG_ON.

===== drivers/scsi/scsi_scan.c 1.78 vs edited =====

proc_print_scsidevice is used for the scsi device listing in
/proc/scsi/scsi, but in addition two drivers (advansys and eata_pio)
are using it to duplicate the same information in their proc_info
method.  Remove that output and make the function static to
scsi_proc.c.  Also remove proc_scsi from the public headers - it
should really be private to the scsi midlayer but I don't think
we can shange the sg procfs name anymore.

into raven.il.steeleye.com:/home/jejb/BK/scsi-for-linus-2.5

Although this driver is ancient and unmaintained, it is still used
by the 53c700 based PA-RISC zalon.  The changes are:

- Add slave_configure entry for zalon
- Moved to new error handling
- changed to irqreturn_t for interrupt handler

This set of 4 patches convert files to use C99 initializers. The patches
are against the current BK.

The attached patch fixes the compile errors in psi240i.c described in
Bugzilla bug #468 at http://bugme.osdl.org/show_bug.cgi?id=468. It was
built against 2.5.68. I do not have the hardware, so I have only
verified that it compiles correctly.

This fixes a mismatch in declaration between "irport_interrupt" in the
header files (returning void) and in the definition (returning
irqreturn_t).

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

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

request_irq requires a handler that returns irqreturn_t,
so mm_interrupt now returns the appropriate value

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

into shaggy.austin.ibm.com:/shaggy/bk/jfs-2.5

This fixes a problem with drivers that have request on the stack for
some operations, like IDE.  If we wake before releasing the request, the
stack may have already disappeared beneath us when the rest of
end_that_request_last() is run.

Fix by making sure the completion is done _last_.

into kernel.bkbits.net:/home/davem/net-2.5

into kernel.bkbits.net:/home/davem/sparc-2.5

into nuts.ninka.net:/home/davem/src/BK/net-2.5

give a clue about what the context was that might have caused
the spurious interrupt.

We no longer hold the host_lock while calling the detect function, so
re-acquiring the lock while (without even unlocking it) in ppa_detect is
very wrong. References to the possibly NULL value hreg can also cause
oopses.

into nuts.ninka.net:/home/davem/src/BK/net-2.5

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

into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk

Patch from Steven Cole.

Here are some spelling fixes for arm.
This was diffed against the current 2.5 tree.

Patch from Eli Carter

# Mon Apr 21 11:11:41 CDT 2003 ejc@rnd-linux-c84
# use-physoffset-define
#
# Use the PHYS_OFFSET #define instead of a hard-coded value.
#
# Diffed against linux-2.5.67-rmk1+1501-3+1506
#
#  arch/arm/boot/compressed/head-xscale.S |    2 +-
#  1 files changed, 1 insertion(+), 1 deletion(-)
#