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

test, since it is needed regardless.

We use the pci host lock so that we lock config space portably while
handling the CMD640 config space via our own routines to avoid pci bios
tripping CMD640 hardware stuff. We need to use this lock in order to
ensure that we lock at a portable layer. Also add the 2.4.19 fixes for
avoiding wrong probes, and the fix noted on the list.

This should do the trick for pnpbios - we load the initial gdt into each
gdt, and we load the parameters into the gdt of the cpu making the call
relying on the spinlock to avoid bouncing cpu due to pre-empt

 - Remove third argument from file_lock security op.  Whether the lock is
   blocking or not cannot make any difference to a security module!
 - Fix the call in sys_flock to pass the translated lock command, not the
   original.
 - Add a call in fcntl_setlease.  If they're going to know about two types
   of lock, let's tell them about the third too.

The patch below does two things:

(i) fixes a small bug in the new partition code
This is the final chunk s/n/slot/. I'll refrain from giving a vi script.
This is uncontroversial.

(ii) removes ancient garbage concerning disk managers
This may well be controversial.

(Long ago, when disks became larger than 500 MB, lots of tricks were
invented to keep DOS happy. Both hardware tricks and software tricks.
One of the software tricks was the invention of boot managers.
There have been many of those. The Linux kernel has had support
for two of them: OnTrack Disk Manager and EZdrive.
More precisely: there have been many versions of both OnTrack Disk Manager
and EZdrive, and the kernel had support for a few of these versions.

I think the time has come to remove the automatic support - every now
and then it bites some innocent user, and the support is not really
needed any longer, and the support is for outdated versions of these
boot managers.

No doubt it will turn out that users still exist that use some form
of this stuff, but I would prefer to support them by explicit
kernel boot parameters, rather than by code that guesses what
might be the right thing to do.

The patch below just rips out the old stuff. Depending on the screams
this might provoke I expect to add some boot parameters.)

This fixes a synchronize_irq() bug: if the interrupt is freed while an
IRQ handler is running (irq state is IRQ_INPROGRESS) then
synchronize_irq() will return early, which is incorrect.

there was another do_IRQ() bug that in fact necessiated the bad code that
caused the synchronize_irq() bug - we kept the IRQ_INPROGRESS bit set for
not active interrupt sources - after they happen for the first time. Now
the only effect this has is on i8259A irq handling - we used to keep these
irqs disabled after the first 'spurious' interrupt happened.  Now what the
i8259A code really wants to do IMO is to keep the interrupt disabled if
there is no handler defined for that interrupt source. The patch adds
exactly this. I dont remember why this was needed in the first place (irq
probing? avoidance of interrupt storms?), but with the patch the behavior
should be equivalent.

Fix PMD typo

Added irq-argument to synchronize_irq to make sound/oss/cs46xx.c
compile again.

the attached patch fixes the scheduler's migration thread startup bug that
got unearthed by Rusty's recent CPU-startup enhancements.

the fix is to let a startup-helper thread migrate the migration thread,
instead of the migration thread calling set_cpus_allowed() itself.
Migrating a not running thread is a simple and robust thing, and needs no
cooperation from migration threads - thus the catch-22 problem of how to
migrate the migration threads is solved finally.

the patch is against Rusty's initcall fix/hack which calls
migration_init() before other CPUs are brought up - this ordering is
clearly the clean way of doing migration init. [the patch also fixes a UP
compiliation bug in Rusty's hack.]

As pointed out by Andrew Morton, this fixes:
	softirq.c: In function `spawn_ksoftirqd':
	softirq.c:416: warning: statement with no effect

This patch fixes the calls to initialize ksoftirqd and the
migration threads.  This really should be done by the initcall
depends patch.

 The check in do_alignment_ldmstm for addr and eaddr being the same is #ifdef'd
out for the ARM922T because they aren't expected to be the same due to the 
different way the MMU sets addr. The ARM920T is just a 922T with more cache, 
and should be treated the same. I've checked on a real ARM920T and it does 
complain loudly every time it fixes up a misaligned ldm/stm unless this 
patch is applied.
 I suspect that the ARM926 should be treated the same way as well, but I can't
find any relevant documentation on ARM's web-site, so have left it out. 

Remove a couple of needless includes from system3.c, and update
mach-types file.

free_pages() oopses if page->mapping is non-NULL.  Ensure that any
rmap datastructures for the page are freed before freeing the
concerned page.

This covers the changes Dominik's made to the core cpufreq code.

Someone included mach-types.h into asm/arch/hardware.h, which causes
the whole kernel to needlessly rebuild when the machine type file is
updated.  Move mach-types.h include into the files that really need
it.

ARM can use the generic rmap.h.  It doesn't need its own version.

This improves interrupts and exceptions returning to user space
by a few of cycles.  We change the requirements for
*_restore_user_regs slightly so we can remove a few instructions.
We also re-shuffle the code to handle pending work.

irq_enter/irq_exit no longer take arguments.  We also use the
x86 methods for hardirq.h and softirq.h; they're sufficient
for ARM.

These macros are no longer required; the generic versions
defined in sched.c are sufficient for ARM.

Replace local_save_flags_cli with local_irq_save.  Remove duplicate
cli, sti, save_flags and restore_flags definitions.

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

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

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

Since we have a signed 32-bit time_t, the fact that y % 4 == 0
will get it wrong in 2100 is irrelevant.

This could be made more efficient by batching the hashtable
flushes but that can be done later.

into atnf.csiro.au:/workaholix1/kernel/v2.5/rgooch-2.5

into atnf.csiro.au:/workaholix1/kernel/v2.5/rgooch-2.5

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

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

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