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

Restore 2.4 behavior when setting the single step breakpoints.

Make the "addr" arg to test_bit "const" to prevent flood of compile
warnings in networking code.

This adds a cache of lastest accessed cluster to inode for sequential
access.

The following is 500M file of FAT-to-FAT copy test, this may be a most
different case in usual operations, because maximum readahead window
flush the all caches.

512 bytes blocksize, 4096 bytes cluster size.

linux-2.5.69-bk12
	root@devron (a)[1232]# time cp file file1

	real    7m58.900s
	user    0m0.267s
	sys     6m44.258s

linux-2.5.69-bk12+patch
	root@devron (a)[1576]# time cp file file1

	real    2m44.309s
	user    0m0.270s
	sys     0m28.631s

This shifts the data position caches from module to per-superblock, and
cleanups.

This removes the obsolete Documentation/filesystems/fat_cvf.txt.

This fixes the return value of ioctl() for enables using the same way as
readdir().

put/get_user() return code check patch from John R R Leavitt
<jrrl@steampunk.com>

This adds large partition (> 128GB) support to FAT.

This silences at least one compile-time warning... :-)

This is needed to match the output of the C compiler.

This header ends up getting included by uClibc (though nothing in it is
used), so this protection is necessary to avoid problems with kernel-only
typedefs.

This is to define `struct file'; apparently some include-file change
removed a previous implicit include.

These registers are now saved in a difference place, but the old code
was inadvertently left in.

	fs/inode.c assumes that any ->delete_inode() will call clear_inode().
procfs instance doesn't.  It had passed unpunished for a while; cdev changes
combined with ALSA creating character devices in procfs made it fatal.

	Patch follows.  It had fixed ALSA-triggered memory corruption here -
what happens in vanilla 2.5.70 is that clear_inode() is not called when
procfs character device inodes are freed.  That leaves a freed inode on
a cyclic list, with obvious unpleasantness following when we try to traverse
it (e.g. when unregistering a device).

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

This allows drivers to resize their tag depth at run-time.

Argh.  Missing initialization in char_dev.c - it's definitely
responsible for crap on unload.  Load side appears to be something else,
though...

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

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

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

agp_init() just printk's a banner. This is unnecessary at this early stage.

Death of a typedef in an earlier cset broke i810fb

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

into hostme.bitkeeper.com:/ua/repos/c/cifs/linux-2.5cifs

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

Alan (or someone else) added a buggy BUG_ON() in ide-cd. We can address >
32-bit just fine with 2kb block size. People are hitting this, just got
one more report today...