- Remove some dead code from mft.c.
- Optimize readpage and read_block functions throughout aops.c so that
  only initialized blocks are read. Non-initialized ones have their
  buffer head mapped, zeroed, and set up to date, without scheduling
  any i/o. Thanks to Al Viro for advice on how to avoid the device i/o.
Thanks go to Andrew Morton for spotting the below:
- Fix buglet in allocate_compression_buffers() error code path.
- Call flush_dcache_page() after modifying page cache page contents in
  ntfs_file_readpage().
- Check for existence of page buffers throughout aops.c before calling
  create_empty_buffers(). This happens when an I/O error occurs and the
  read is retried. (It also happens once writing is implemented so that
  needed doing anyway but I had left it for later...)
- Don't BUG_ON() uptodate and/or mapped buffers throughout aops.c in
  readpage and read_block functions. Reasoning same as above (i.e. I/O
  error retries and future write code paths.)

- Streamline the usage of sector_t over the strategy routines in question a
   bit. Streamline the do_request code in ide-disk.c.

- Improve the readability of start_request in ide.c.

- Remove obsolete/nowhere used stuff from hdreg.h.

- Splitup special_t into classical flag field.

- Use only a single field to determine the capacity of a drive.  Make this
   field and the code paths it follows as far as possible use the sector_t
   instead of a hard coded integer types.  This increases the chances that at
   some distant point in time we will indeed be able to use 64 bit wide sector_t
   entities. (Disks are getting huge those times now...)

- Initialise the per-request_queue readahead parameter properly,
  rather than the dopey "if it's zero you get the deafult"
  approach.

- Permit zero-length readahead.

- 80-columnify mm/readahead.c

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

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

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make

Get rid of traces of the old-style ALL_MOBJS variable.

This also fixes the following issue, which could cause a warning with
certain configs:

Makefiles (legally) do:

obj-$(CONFIG_SND_AD1848) += snd-pcm.o snd-timer.o snd.o
obj-$(CONFIG_SND_CS4231) += snd-pcm.o snd-timer.o snd.o snd-rawmidi.o

so when the first option is set to y, the second to m, we have e.g.
snd-pcm.o on both $(obj-y) and $(obj-m). We correctly don't build
the modular version in this case.

However, if snd-pcm.o was a multi-part object, we did automatically
generate a link rule for both the modular and the built-in version, 
which caused a warning - that's now fixed.

 - switch md_error() to struct block_device * - just cleaning up
   after ->bi_dev switch.

 - bdevname() switched to struct block_device *.  Old variant (taking
   kdev_t) renamed to __bdevname() (very few callers remain).  This
   allow to drop ->b_dev conveniently - it's duplicated by ->b_bdev
   and most of remaining users were bdevname(bh->b_dev) in various
   places.

 - *NOW* all places that (re)assign ->bi_dev have relevant struct
   block_device *.  ->bi_bdev (struct block_device * equivalent of
   ->bi_dev) introduced, ->bi_dev removed, users updated.

 - block/loop.c - switch ->lo_device to struct block_device *.

 - (JFS) removes ->dev from struct jfs_log - it's duplicated by
   ->bdev.  Old users of ->dev updated.

 - md/linear.c - bring struct block_device * into private data.

 - this one is interesting and will play in the next series as well;
   affected place is fs/block_dev.c::do_open().  We check if bdev is
   a partition (same way it is done in generic_make_request()) and
   if it is - open entire disk and put pointer to its bdev into a
   new field bdev->bd_contains.  Otherwise (non-partition) we
   set bdev->bd_contains to bdev.  Corresponding cleanup done in
   blkdev_put() (and failure path in do_open()) - when the last opener
   goes away we close bdev->bd_contains if bdev is a partition (i.e.
   not equal to its ->bd_contains) and set it to NULL.
   Immediate effect is that we can get from bdev of partition to
   bdev of disk when submitting a bio, but it also opens a way
   to handle partition-parsing in a sane way.  That will be done
   in the next series.

 - md/raid1.c - bring struct block_device * into private data.

 - md/multipath.c convert to bio, compile fixes, bring struct
   block_device * into private data.

 - switch loop_set_fd() to struct block_device

 - switch blk_{get,set}_readahead() to struct block_device *

 - switch block_ioctl() to struct block_device *

 - new helpers: queue_hardsect_size() and bdev_hardsect_size().  Analogous
   to get_hardsect_size() for queue and struct block_device * respectively
   Most of get_hardsect_size() callers converted to these.

 - remove abuses of blksize_size[] and (late) hardsect_size[].  Mostly
   drivers/s390/char/*, BTW...

 - remove abuses of blksize_size[] and (late) hardsect_size[].  Mostly
   drivers/s390/char/*, BTW...

Remove unnecessary linux/bitops.h from fat/inode.c.

This patch cleans up fat_clusters_flush().

This patch does misc cleanup.

OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

This patch makes detection of a FAT filesystem more exact by checking
the first FAT entry. 

Currently fatfs disregards most wrong cluster chains, and only continues
processing. 

This fixes it.  If a wrong cluster chain is detected, change filesystem
to the read only, and return the error code. 

 - Revoke the TCQ stuff. Well having it for some time showed just nicely what
   has to be done before it can be included cleanly. But it's just not ready
   yet.

   For more explanations please simply track the usage of the special field of
   struct request - *both* in the generic request handling code and in overall
   driver code.

The ABC extensions are not in the official kernel, so remove references
to them.

No idea why that didn't hit me during testing ;-(

Forward port changes from 2.4.19-pre, originally by Keith Owens.
This driver used to build a module target called "aic7xxx_mod.o" and
introduced the MOD_TARGET variable to rename it to "aic7xxx.o" at
modules_install time.
    
Now, we just build "aic7xxx.o" directly, which becomes possible after
renaming aic7xxx.c to aic7xxx_core.c, as done in 2.4.19-pre.