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

This also cleans up the machine check code generally.

into samba.org:/home/paulus/kernel/for-linus-ppc

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

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

into kernel.bkbits.net:/home/davem/sparc-2.5

into kernel.bkbits.net:/home/davem/net-2.5

- Merged AES code from Adam J. Richter <adam@yggdrasil.com>
- Add kconfig help and test vector code from
  Martin Clausen <martin@ostenfeld.dk>
- Minor cleanups: removed EXPORT_NO_SYMBOLS (not needed for 2.5),
  removed debugging code etc.
- Documentation updates.

into kroah.com:/home/linux/linux/BK/gregkh-2.5

Since we killed off the broken 486 strings copies,
the config item isn't needed any longer.

Next in line for the -W cleanups is this patch from Willy
which I've been carrying since 2.5.29 or so. Should be no
functional differences, just no more warnings when we compile
with -W

s/boundry/boundary/

Without this fix, compiling with CONFIG_DEBUG_SPINLOCK
dies with an unknown variable error..

This looks extremely suspect to me, and seems like
it will prefetch past the end of the pmd, which is a no no.

Can't remember where this came from, but its been around
for quite a while. Prints the parent (tracer) pid if
its being traced.

The first of many...

From 2.4

Silly typo caused strange corruption.

With this fixed, agpgart almost works again on x86-64
(change_page_attr() seems broken there)

From 2.4

Cset 1.808 in 2.4 never got propagated forward to 2.5

It's pretty much the same fix as below (s/!=/</), but with the following
changes
 - This was a patch to pci_alloc_consistant(), which now wants to be
   dma_alloc_coherent()
 - Removal of the u32 cast

Missed forward port from 2.4. ACKed by GregKH

From 2.4

From 2.4, and munged.

From 2.4

Fix incorrect CONFIG_ name

From 2.4 a few months back. With a few edits by
myself to remove the wacky bits of the diff that
backed out fixes. (*Sigh*, Intel).

Been carrying this for ages..

From Jens Axboe:

   This is for changers, we may need more than the default
   5 second timeout for loading a disc since it may require
   moving stuff around :)

From Jens Axboe:

   Only fall back to plain READ, if the device says it doesn't
   support the READ_CD opcode. This is the true error for which
   we want to do the fall back, not for any generic error.