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

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

but somehow are not handled by the DV state machine.  This ensures that
the behavior seen before DV is restored in the event of a DV state machine
failure.

but is still required in earlier kernels.

on some tape and cdrom devices.

counted toward the load average. 

This allows the assembler to operate without generating this file.

The original bug was that the 2.4.X declaration was used unconditionally.

Daemonize the kernel threads used for domain validation.

Restore a call to ahc_assert_atn() that was inadvertantly lost when the
asserting atn diagnostic was added.  This, among other things, resulted
in driver negotiation failures with devices that initiated negotiation
(e.g. most IBM drives). 

Correct a compilation warning that occurs when debugging code is
compiled in.

AIC7XXX_REG_PRETTY_PRINT.  The constant rebuild is due to the build
process deciding that the pretty_print.c file is an intermediate file
and that problem lies elsewhere.

Remove incorrect dependency on SCSI_AIC7XXX_BUILD_FIRMWARE (the
wrong driver noless) and AIC79XX_REG_PRETTY_PRINT.  The constant
rebuild is due to the build process deciding that the pretty_print.c
file is an intermediate file and that problem lies elsewhere.

* version code checks for pre-2.4 version
* !__KERNEL__ stuff in headers.

Makes this generic info reflect current behavior.

Simple patch to invoke hcd->stop() in task context, as
required.  When Cardbus works again (broken in 2.5.53
unless it's just me), this will get rid of some oopsing
when folk physically eject the device, with no shutdown.
As well as making other "hc died" faults behave better.

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

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

into halogen.(none):/home/davej/src/kernel/2.5/agpgart

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

With Martin's blessing, here is the s390x syscall compatability stuff.

Another one that James noticed..

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

I missed one hunk when splitting the patch for removing
try_inc_mod_count().

The might_sleep() check in kmm_cache_alloc() is currently disabled if slab
debugging is disabled.

Fix that so it's enabled if might_sleep debugging is enabled.

add_disk_randomness() is causing a context switch per disk request.  It
is scheduling process-context work one timer tick in the future for
every request.

But is has a buffer for this, so change it to not set up the
process-context work until that buffer is half full.

The patch reduces the context switch rate during a 20 megabyte/sec
write to scsi from 150/sec to 50/sec.

George Anzinger identified the following problem: when a secondary CPU is
coming up, it calls printk() before it is "online".  It calls the console
drivers before its per-cpu storage has been prepared.  And the vga console
driver does a mod_timer().  This CPU's timers have not yet been initialised;
it is not clear why this doesn't oops - George thinks it is because virtual
address zero is still accessible at that time.

I believe the right way to fix this is to change printk so that a not-online
CPU will not call the console drivers.  Because printk should always be
callable.  If the CPU is not online the message is buffered, so the next
caller to printk who is online will actually display it.

ia64 has been doing exactly this for ages, so we can remove the
arch_consoles_callable() hook and just open-code the cpu_online() test in
printk.



That fixes things up for the secondary CPUs.  But this change causes a
problem for the boot CPU: it is being marked online very late in boot, so the
printk buffer is being displayed much later than we would like.

I believe that the solution to this is to mark the boot CPU online much
earlier.  So in this patch we call the new arch-provided function
smp_prepare_boot_cpu() immediately after the boot CPU's per-cpu areas are set
up.  Its mandate is to (at least) mark the boot CPU "online".

The change has been reviewed by davem and rth.  No comments were received
from the other arch maintainers.