Patch 960/1 (Peter Teichmann):
   NWFPE patch to be more compliant to IEEE-754

1. The RND/URD instruction was handled as int_to_float(float_to_int
   (number)) which is wrong because it only works for floating point
   numbers that fit in an integer.

2. The FLT instruction was setting the rounding precision for
   extended precision calculations, which is not necessary
   (probably a historic relict) but has undesirable side effects
   on all extended precision calculations.

replication across each processor type, each handling alignment of
addresses slightly differently.  We unify this mess, and allow for
greater flexibility in the per-CPU architecture TLB handlers.

We also start to remove the ARM cache.h -> cpu_*.h -> proc-fns.h mess
making the code cleaner and easier to follow.

Documentation describing the expected behaviour of each TLB function
for the 32-bit ARM processors is also included.

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

-
 make vma->vm_next_share and vma->vm_pprev_share
  a proper list.h list as well.

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

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

the lvm-patch that went into 2.5.5 missed the changes in lvm.h and is
still not compileable. This patch adds those changes. The kernel i'm
running right now has this patch and /var and /home on lvm.

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

A forward-port of all the .text.exit fixes which went into
2.4.   Also contains a couple of s/MINOR/minor/ changes.

Al updated Documentation/filesystems/porting with 2.5 changes but there
is no mention of lseek.  The following patch, against 2.5.5, adds lseek
to the list of functions that no longer are called with the BKL.

	Robert Love

The attached patch implements proper locking in ALSA lseek methods.
Note ALSA has 3 lseek implementations, but only:

	sound/core/info.c :: snd_info_entry_llseek()

requires locking.  I wrapped the function in the BKL.  According to
Jaroslav Kysela the gus_mem_proc method is only called from above.  The
third lseek, in hwdep.c, clearly doesn't need locking.  Without this
patch, the above lseek is not safe.

	Robert Love

This patch add the validity check of 2 values (fats, reserved). These
values must not be 0.

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

Here enclosed patch for eata.c, eata.h, u14-34f.c, u14-34f.h
to be applied to lk-2.5.5.

eata.c:
       + Remove any reference to virt_to_bus().
       + Fix pio hang while detecting multiple HBAs.
       + Fixed a board detection bug: in a system with
         multiple ISA/EISA boards, all but the first one
          were erroneously detected as PCI.

u14-34f.c:
       + Remove any reference to virt_to_bus().
       + Fix pio hang while detecting multiple HBAs.

After BKL was moved from the VFS into the filesystem's methods in the lookup
call, we do not need to check BKL is actually held (we know it is not).
This patch patch removes unneeded lock_depth check.
Without this patch reiserfs cannot be used on SMP.

2.5.5 Oopses at boot time with a disk in a zipdrive.
With this patch all is fine. I have not read the
patch, certainly not checked it for correctness,
just observed that it works for me.
I think the author is Rich Baum.

Andries

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

use spin_[un]lock_irq{save,restore}, instead of defining static
inline functions to do the same thing (but possibly in a non-portable
way).

and wavelan_cs to new wireless API.

into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk

data.

its modes of operation.

help texts.

checksum functions.

generic local_irq_save() where appropriate.  (None of these are ever
going to be used on a SMP ARM machine).

into are.twiddle.net:/home/rth/BK/linux-alpha-2.5

into elte.hu:/home/mingo/BK/mine/linux-2.5

save_flags/cli/restore flags sequence with spin_locks.

PCI/dual 16950 UART chip, and adds this entry to pci.ids.  I downloaded the
datasheet today and verified that 9521 is the correct device id.