The following patch fixes a few compiler warnings, as well as provides
blk_init_queue() with the appropriate arguments. Please review for
inclusion. Thanks to Jens Axboe for fixing the casting hack in
the previous version of this patch.

Don't know what exactly happened, but somehow, the ZX1 support is
in your tree twice. This patch drops one of them, and also adds
in Intel i845 support to make up for it 8-)

Another one from Brian Gerst. Still applies to 2.5.18

Seperates adfs_sb_info from struct super_block.

Andrew Morton found that egcs was miscompiling the per-cpu area code
on x86. This patch updates the check, and documentation accordingly.

TIMEOUT_VALUE was killed from blk.h and moved to drivers that need it (like this one)
DEVICE_REQUEST is also dead, so we init the queue with the driver request handler

Conversion done by William Irwin a good while ago.

Variant of a patch in 2.4 by Steven Whitehouse.

Originally from: Jeremy Elson <jelson@circlemud.org>

As per the old comment, this patch adds checking of the return
value of setup_arg_pages() and aborts cleanly. From 2.4
(also a missing GPL tag)

Stale cruft, and what looks like a merge error.

Allow user to define the upper limit of number of interrupts generated

Should allow for things like adjusting readahead on raw devices.

Patch from 2.4 sets the maximum size of the queue in a more sensible manner

region handling cleanups

o check request_region result
o handle failure gracefully

o printk levels
o check_region -> request_region cleanups
o allocated region releasing on failure

simple region handling cleanups.

o Check misc_register return code
o request_region() return code checking
o graceful failure

o Check request_region result

o check request_region result
o Handle failure gracefully

Wow, someone found some new devices for this beast..

checks return codes, and sanitises resource allocation.

o  mention a quirk in the athlon smp detection
o  mark some use-once paths as __init

The usual check_region -> request_region work, plus freeing
of resources on failure path.

Odd, this is the missing half of the recent fix where we prefetched
too far. Not sure how this bit got dropped. Without it, we still prefetch
past the end of a range of memory.
Also small compiler hint microoptimisations

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

The following should allow the affected architectures to build in
2.5.19 as currently there will be two definitions of
copy_siginfo_to_user and if an architecture defines its own
siginfo_t it MUST define copy_siginfo().