dm_suspend(): Stop holding the read lock around the while loop that
waits for pending io to complete.

queue_io() was checking the DMF_SUSPENDED flag rather than the new
DMF_BLOCK_IO flag.  This meant suspend could deadlock under load.

Give each device its own io mempool to avoid a potential
deadlock with stacked devices.  [HM + EJT]

There's a bug in the dm-stripe.c constructor failing top check if enough
destinations are handed in. [Heinz Mauelshagen]

minor change for dm-stripe.c. Tests for correct chunksize before it allocates
the stripe context. [Heinz Mauelshagen]

check_device_area was comparing the bytes with sectors.
[Stefan Lauterbach]

No need to validate the parameters if we are doing a
REMOVE_ALL command.

Return -ENOTBLK if lookup_device() finds the inode, but it
is not a block device. [Cristoph Hellwig]

An error value was not being checked correctly in open_dev().
[Kevin Corry]

Four constants:
   DM_DIR,
   DM_MAX_TYPE_NAME,
   DM_NAME_LEN,
   DM_UUID_LEN

Were being declared in device-mapper.h, these are all specific to
the ioctl interface, so they've been moved to dm-ioctl.h.  Nobody
in userland should ever include <linux/device-mapper.h> so remove
ifdef __KERNEL guards.

The writepage-removal patch broke filesystems which do not want to
support writeable mappings.

Fix that up by making those filesystems point their mmap vector at the
new generic_file_readonly_mmap().

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

This patch addes the new restart_block field support to m68knommu
thread_info.h.

This patch adds a definition for TASK_UNMAPPED_BASE in m68knommu
process.h.  Recent changes need a definition for this, although its
value is unsed for nommu targets.

The patch include cache.h in m68knommu hardirq.h.

Cleans up compile problems, and make its consistent with
all other architecture hardirq.h files.

This changes m68knommu current.h to include the linux/thread_info.h
instead of asm/thread_info.h.  This is needed to get the restart_block
definition from linux/thread_info.h first.

This fixes the broken ELF_CORE_COPY_REGS macro for m68knommu arch.  It
is missing a ";" after the pr_reg[16] setting, and attempts to set the
non-existant a2 field.

This removes use of the depricated sys_security system call entry for
the m68knommu architectures.

This adds spinlocks around calls to generic kernel signal routine calls.

This adds the missing argument to do_fork() calls in m68knommu arch
process.c

This fixes the use kstat_cpu in m68knommu arch ints.c Replcae obsolete
use of kstat.irqs.

This little patch changes the way button release events are reported
by the sonypi driver to the application: previously, separate
release events were detected for each button. However, many buttons
(example: the jogdial, the capture button, the back button etc) share
the same release event.

The attached patch propagates a single 'ANYBUTTON_RELEASED' event
to the userspace, leaving all state machine intelligence to the
application.

Kunihiko IMAI should be credited for his ideas and tests.

The enclosed patch fix compile problems and adds all the diffs which
were still missing from 2.5.51.

This covers a lot of ground in the Linux1394 SVN tree.  I haven't had
time to keep in sync with you in a more granular way, so here's a
bohemoth patch.  However, consider it well tested.

In order to speed up NFS reads, we attempt to copy directly from
skbuffs into the pagecache pages. As we cannot do XDR decoding in the
soft interrupts, we attempt to estimate the size of the RPC header (+
attributes,...) that will precede the actual data that goes in the
pagecache. If we get the estimate wrong, the XDR decode routines
perform a realignment of the data into the pagecache.

In the existing code, we do a multi-page kmap() from the xdr_buf into
an iovec array, in order to do the shift.

The following patch adds tools for doing the realigment without going
through the iovec array (and without having to do the deadlock-prone
multi-page kmap()).

It also adds the 2 helper routines xdr_read_pages()/xdr_write_pages()
which will be needed for NFSv4 reads/writes in order to add pre/post
operation GETATTR calls.

 - Move the encoding/decoding of the actual COMPOUND XDR header out of
   encode_compound()/decode_compound().

 - Make each NFSv4 operation 'decode_' routine also take care of
   decoding its own header, and checking it for correctness.
   Also allows us to get rid of the 'nfserr' parameter...

This fixes a couple of incorrect XDR buffer reservations.  The values
passed to RESERVE_SPACE() must reflect precisely the number of bytes
that we wish to send down the wire.