Traditionally, we allocated the private array of port parameters based on
the detected board->num_ports, and then called the init_fn with the board
pointer (which points into the global table.)  Some init_fn implementations
modify num_ports, which therefore affects the global table.  Unfortunately,
this means that if the init_fn increases num_ports (because we have two
almost identical cards, the first with a smaller number of ports than the
second), we will overwrite memory which hasn't been allocated to us.

This cset no longer passes the board pointer into the init_fn, but instead
allows the init_fn to return the number of ports found, or zero to use the
default value in board->num_ports, or negative error number.

uart_event() only has one purpose, which is to wake up any pending
writers via the line discipline.  Rename it to reflect its real
functionality, and drop EVT_WRITE_WAKEUP.

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

- Convert to new configuration language and fix up HEX config symbols
- Fix build errors for !CONFIG_KALLSYMS case
- Add module list to oopsen.
- Add POLLREMOVE

For many moons, we've been executing identify_cpu()
on the boot processor twice on SMP kernels.
This is harmless, but has a few downsides..
- Extra cruft in bootlog/dmesg
- Spawns one too many timers for the mcheck handler
- possibly other wasteful things..

This seems to do the right thing here, and has been
acked (after some minor squibbles) on l-k.

Without the below patch, my HT 2-way prints out
"CPUS Done 4294967295" on boot, which whilst amusing
is somewhat exaggerated.

The machine check initialisation prints some blurb
which makes the capabilities dumping a little untidy.
By initialising it slightly later, we get something that
looks a lot better.

  We've uncovered yet another kmap imbalance in the new RPC code.  This
looks like it might be the last one (my debugging printks have been
unable to unearth any more).  One line fix + 4 line comment appended.

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

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

a compile failure.

This is a minor cleanup that removes two instances of CONFIG_X86_TSC
(lets the compiler optimize it out), and adds a warning message should
anyone pass "notsc" to a kernel compiled w/ CONFIG_X86_TSC (which
ignores it).

This is basically a forward port of a patch I got into 2.4 a while back.

I like Alan's idea: IGNLABEL("HmacRxAccepted")

From Matthew Dobson.

This final patch from Matthew cleans up a few leftovers which were noted
after the code had been reviewed and tested a bit in the -mm patchsets.

1) Update register_XXX and arch_register_XXX functions to return int
   instead of void.  Functions calling these functions should know if
   they completed successfully to take appropriate further registration
   action, or not bother.

2) Drop some pointless error checking in the arch_register_XXX
   functions.

From Matthew Dobson.

Create and use node_online_map.

This patch creates a node_online_map, much like cpu_online_map.  It
also creates the standard helper functions, ie: node_online(),
num_online_nodes(), node_set_online(), node_set_offline().

This is used by driverFS topology to keep track of which Nodes
are in the system and online.

From Matthew Dobson.

Create and use memblk_online_map.

This patch creates a memblk_online_map, much like cpu_online_map.  It
also creates the standard helper functions, ie: memblk_online(),
num_online_memblks(), memblk_set_online(), memblk_set_offline().

This is used by driverFS topology to keep track of which memory blocks
are in the system and online.

From Matthew Dobson.

Create nodeX/meminfo files for DriverFS Topology.

This patch adds code to DriverFS Topology to expose per-node memory
statistics.  This information is exposed via: cat nodeX/meminfo

The patch also adds 2 helper functions to gather per-node memory info.

From Matthew Dobson.

Update/Create i386 specific files for DriverFS Topology.

This patch creates the i386 specific files/functions/structures to
implement driverfs Topology.  These structures have the generic
CPU/MemBlk/Node structures embedded in them.

This patch also creates the arch-specific initialization routine to
instantiate the topology.

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 :(

- Fix namespace ordering, which was causing breakage
- Enhance some error messages

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