into nuts.ninka.net:/home/davem/src/BK/net-2.5

Patch by Matthew Wilcox.

Allows all architectures to simply include the drivers/ide/Kconfig file.

Patch by Benjamin Herrenschmidt, minor fixes by me.

Unexpectedly there are some taskfile IO bugreports,
so bring back old code and add taskfile IO config option (default y).
This aids testing and lets people use safe(?) old code.

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

From: Manfred Spraul <manfred@colorfullife.com>

Martin found out what caused the deadlocks with 2.5.70 and SDET: I forgot
to initialize proc_lock during fork().  Usually this works, because the
parent lock is unlocked.  But a proc lookup during fork can cause it to be
locked, and then the system locks up.

1) Fix the comments for the migration_thread.  A while back Ingo
   agreed they were exactly wrong, IIRC. 8).

2) Changed spin_lock_irqsave to spin_lock_irq, since it's in a
   kernel thread.

3) Don't repeat if the task has moved off the original CPU, just finish.
   This is because we are simply trying to push the task off this CPU:
   if it's already moved, great.  Currently we might theoretically move
   a task which is actually running on another CPU, which is v. bad.

4) Replace the __ffs(p->cpus_allowed) with any_online_cpu(), since
   that's what it's for, and __ffs() can give the wrong answer, eg. if
   there's no CPU 0.

5) Move the core functionality of migrate_task into a separate function,
   move_task_away, which I want for the hotplug CPU patch.

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

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

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

It was broken on at least ppc32 & sparc32, and the debugging it
offered wasn't worth it any more anyway.

local_irq_save() is called at the beginning of speedstep_detect_speeds,
but local_irq_restore() is not called on I/O errors.

Intel seems to have changed their mind, and now document the detection
process for speedstep-enabled Pentium III Coppermines:

	http://www.intel.com/support/processors/sb/cs-003779-prd24.htm

Here is a patch.

I kept the setup parameter, but it might be removed now?

This patch moves the old board-specific SH code

This gets the toplevel arch/sh stuff in sync with the current SH 2.5
tree.

This bit is left from the zlib changes.  According to Paul, the zlib
bug is already caught in userspace pppd, but not in the kernel ppp
code.  With this patch, there is one potential hickup less in ppp.