There's still an #ifdef in there for CONFIG_BLK_DEV_INITRD, but at
some point it just gets too many files, so accept that for now.
There's also a #define BUILD_CRAMDISK in there, which should be either
made a config option or removed...

The mount_initrd check can be moved into initrd_load(), so that we
have all initrd code consolidated in one #ifdef'd section now.

Currently, we would try to read in a ramdisk image from floppy, if
o root device is /dev/fd*
o "load_ramdisk=1" on the command line
o CONFIG_BLK_DEV_INITRD is not set, or "noinitrd" on the command line.

Relax the last restriction, which only makes things more complicated for
no reason, and changes behavior depending on an unrelated config option.

This just moves a bit of logic out of prepare_namespace() into
initrd_load(), which means that we now don't reference handle_initrd()
anymore if CONFIG_BLK_DEV_INITRD is not set (we wouldn't call it anyway),
so we can put some bits of code under a common #ifdef CONFIG_BLK_DEV_INITRD.

When CONFIG_BLK_DEV_INITRD is not set, mount_initrd will always be
0, so initrd_load() won't be called. However, we need a stub to make
the compiler happy.

If initrd_start is 0, initrd_load() -> rd_load_image() -> open("dev/initrd")
will fail anyway, so no need for the explicit check here.

As we all know, strncmp() returns 0 for match...
Obviously nobody uses this codepath since it never worked, but let's fix
it anyway.

Again, just get rid of some #ifdefs by moving MD setup into
its own file which is only compiled when CONFIG_BLK_DEV_MD is set.

o prepare_namespace() is called before free_initmem(), so it can
  be __init.
o all static data in do_mounts.c can be __initdata for the same reason.
o move the __init into its standard location between return value
  and function name.
o root_device_name can be a char *.

Get rid of a couple scattered #ifdef CONFIG_DEVFS_FS in init/do_mounts.c
by moving the devfs code into its own file and using stubs when it's
not selected.

Changes in the config system have obsoleted these files.

Moves the #ifdef into the function to improve readability.

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

Use list_for_each_entry() instead of open code.

Convert fs/bio.c and fs/jfs/jfs_metapage.c to use the mempool_alloc_slab
and mempool_free_slab helper functions.

fix two tpyos

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

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

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

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

This makes use of 'check_gcc' facility when compiling for a Crusoe
processor in order to choose the correct -falign or -malign compiler
flags.

This adds suspend/resume capabilities to the meye driver.

This makes the sonypi driver forward the VAIO jog-dial events directly
to the input subsystem as mouse wheel events.  This way one is not
required anymore to have an external daemon polling /dev/sonypi if
interested only in jogdial events.

In most cases the fix is to add an struct module * member to the operations
vector instead and manipulate the refcounts in the callers context.

For the ALSA cases it was completly superflous (when will people get it that
using an exported symbol will make it's module unloadable?..)

since we now properly reference-count the allocations and thus can't
be freeing the thread structures from underneath the task running on
another CPU.

Move "free_uid(p->user)" and "security_task_free()" to __put_task_struct(),
so that we're guaranteed to always have a user structure pointer.

Please accept this large patch against 2.5.62bk4 to update the
Fusion-MPT driver from 2.03.01.01 to 2.05.00.03.

This version contains full 2.5 kernel support (add, configuration &
removal of disks, new module hooks), performance enhancements, removal
of obsolete code that is 2.4 (or earlier) specific and removal of blank
spaces at end of lines.  Tested overnight on 2.5.62bk3 and ran some
tests against bk4 this morning on both machines.  Things appear to be
fine - have not tested the two failure conditions today.

The driver has been tested on two different platforms:

- P4 4-processor
   o boot controller
   o built into kernel
   o disk add, configure, remove
   o bus, target reset
   o device offline cases
   o cross channel I/O stress tests w/ Fibre and SCSI

 - Athlon uniprocessor, IDE boot
   o Ran a test that repeatedly loads the driver, mounts disks, runs a
     short I/O test (20mins) then unload the driver components in a
     different order

Failures:
   o Unable to boot if boot controller is built as a module - pivot_root
     fails (Happens if IDE or SCSI boot)

   o Problems when formatting large SCSI disks.  On P4 w/ 2.5.60, there
     were no difficulties formatting a 36GB disk.  On Athlon, mkfs.ext2
     would never send a write command to the driver (verified w/ SCSI
     trace and driver debug).  Reads completed successfully.  mkfs.ext2
     would not exit and is shown as a running process.

     Smaller partitions were formatted correctly.  W/ 2.5.62 failures on
     P4 and Athlon.

     Same error with other drivers. 100% reproducible.

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

which is needed to keep track of process usage counts correctly and
efficiently.

Cleans up the list handling in a few places within the pci core.

Bill Irwin was talking about hw_interrupt_type.set_affinity and kirq.
When I went looking, I failed to find this initialization.

Here are some nice, easy-to-find, named initializers.

We're calling mmdrop() under spin_lock_irq(&rq->lock).  But mmdrop
calls vfree(), which calls smp_call_function().

It is not legal to call smp_call_function() with irq's off.  Because
another CPU may be running smp_call_function() against _this_ CPU, which
deadlocks.

So the patch arranges for mmdrop() to not be called under
spin_lock_irq(&rq->lock).