From Matthew Dobson.

Update/Create core files for DriverFS Topology.

This patch creates the generic structures that are (will be) embedded in
the per-arch structures.  Also creates calls to register these generic
structures (CPUs, MemBlks, & Nodes).

Note that without arch-specific structures in which to embed these
structures, and an arch-specific initialization routine, these
functions/structures remain unused.

The global page accounting functions are currently using "+=" against a
ulong.  But this can happen at interrupt time as well, and "+=" is not
atomic against interrupt-time modification of the same word.

Change it to use local_irq_save()

Patch from Andreas Dilger <adilger@clusterfs.com>

If you have ext2_fs.h and ext3_fs.h included at the same time, we are
missing one define used in ext3_should_journal_data() and
ext3_should_order_data() as part of the test_opt() macro (which
defaults to the ext2 definition if both are present).

If a task is running in state PF_MEMALLOC and is interrupted, the page
allocator will treat allocations by the interrupt handler as
PF_MEMALLOC as well.

Detect that, and stop it.  Also tidies things up a little in there.

Currently we are storing filenames which are 16-chars or less
inside struct dentry itself and then separately allocating
larger names.

But this leaves spare space in the dentry - the dentry slab cache
is using cacheline alignment.   In my build, struct dentry is 112
bytes so there are at least an additional 16 bytes in there.

And the number of files which have names in the 16-32 char range
will be significant.

So Manfred's patch changes the dcache code to utilise _all_ the space
between the last member of the dentry and the start of the next cacheline.

Use prepare_to-wait/finish_wait to avoid bouncing the waitqueue
spinlock between the waker and the wakee all the time.

Currently if you use the raw driver against /dev/hda1 while it has an
fs mounted, everything gets confused and the kernel locks up or oopses.

Al said to use bd_claim().  This prevents the raw driver from being
able to open the device under these circumstances.

There is value in being able to read the raw device while there's a
filesystem mounted: to poke around at the disk without interacting with
the kernel's caching.  You can still do that, with an O_DIRECT open of
/dev/hda1.

The arg to ZERO_PAGE() doesn't get evaluated on ia32 :(

This is the M68K mmuless port code maintained by Greg Ungerer and used
by Snapgear for all sorts of bits of hardware. No shared files included
in this chunk of patches. This matches 2.5.45-uc1 which is the stuff that
has been in my tree for a bit combined with Kconfig changes

This is much like the old m68k amiga/st loader world. Its a relocating
loader with optional compression. Shared libraries and A5 sharing stuff
is all handled by the userspace/libs

This is the V850 support maintained by Miles Bader at NEC

Again this is just arch and include/asm- files. It matches 2.5.45-uc1 + v850
fixes which is close to what was in my old tree (some clean up done since then)
plus Kconfig

Update DIGI entries
Update IRDA entries
Add Voyager
Put Device mapper under D

(With bios changes merged)

Again so we dont forget to fix this

So we dont forget to actually fix the lack of error handling

These are from inl going back to 32bit

Som boards dont seem to be in spec