From 2.4 with some 2.5 mangling from Robert Love.

From Zwane Mwaikambo, this diff makes sure we don't
poke reserved bits on the P4.

make mrproper misses some files..

Missing kill_sb member meant that futexfs died
a death when someone tried to mount it.

This patch from Ravikiran G Thirumalai removes
cacheline bouncing of apic_timer_irqs

Straightforward diff to allow longer names
for PCI devices

- Standardise usage on IA-32 instead of a mix of IA32 and ix86.
- Add some missing options.
- Fix up some options.

From 2.4

From 2.4

Files moved, so the comments should be updated
to reflect their new locations.

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

input_register_device() usually does that, but some drivers will call
input_event() before registering to pre-load the absolute values in
struct input_dev in an easy way.

standard for extended keys.

work.

can be set for keys over 128.

  - Kill unused variable and end-of-line whitespace.
  - s/M68K/M68k/

..and minor() cleanups

into groveronline.com:/root/bk/linux-acpi

That previous patch got rid of a boot time might_sleep() warning,
but I noticed two later on:

  - kmalloc() needed SLAB_ATOMIC

  - destroying the 'pools' driverfs attribute could sleep too

The clean/simple patch for the second one tweaked an API:

  - pci_pool_create() can't be called in_interrupt() any more.
    nobody used it there, and such support isn't needed; plus
    that rule matches its sibling call, pci_pool_destroy().

  - that made its SLAB_* flags parameter more useless, so it's
    removed and the DMA-mapping.txt is updated.  (this param
    was more trouble than it was worth -- good that it's gone.)

Nobody (even DaveM) objected to those API changes, so I think
this should be merged.

into groveronline.com:/root/bk/linux-acpi

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

This adds initial support for NFS direct I/O in the 2.5 kernel.  many
have asked for this support to be included in 2.5.  this patch does not
provide working NFS direct I/O, but i'm sending what i have now so that
it can be included before October 20.

NFS direct I/O is enabled by its very own kernel config option.  when
enabled, the NFS client won't build to prevent people from using this and
possibly corrupting their NFS files.  later i will send a patch that
finishes the implementation.

[ Config option currently disabled ]

This makes the NFS client copy the page->index field into its read and
write request structures (struct nfs_page) when setting up I/O on a
page.  this makes it possible for NFS direct I/O support to reuse
existing NFS client subroutines, and helps eventually allow NFS I/O to
and from anonymous pages.  it is a prerequisite for NFS direct I/O
support.