into groveronline.com:/root/bk/linux-acpi

A driver for the Mux serial ports in some PA-RISC servers from Ryan Bradetich.

into groveronline.com:/root/bk/linux-acpi

Clean up poll queue handling, avoid doing any wait-queue operations
when we only want to get the current state.

(Yes, they should probably use __stringify() instead).

This patch provides basic x86 support for modules.

This is an implementation of the in-kernel module loader extending
the try_inc_mod_count() primitive and making its use compulsory.
This has the benifit of simplicity, and similarity to the existing
scheme.  To reduce the cost of the constant increments and
decrements, reference counters are lockless and per-cpu.

Eliminated (coming in following patches):
 o Modversions
 o Module parameters
 o kallsyms
 o EXPORT_SYMBOL_GPL and MODULE_LICENCE checks
 o DEVICE_TABLE support.

New features:
 o Typesafe symbol_get/symbol_put
 o Single "insert this module" syscall interface allows trivial userspace.
 o Raceless loading and unloading

You will need the trivial replacement module utilities from:
	http://ozlabs.org/~rusty/module-init-tools-0.6.tar.gz

By Kai Germaschewski.

This patch adds a -DKBUILD_MODNAME to the kernel compile, which
contains the base of the module name which is being built.

 - Some sreorganization of the c_flags since they're needed for
   generating modversions (.ver) and compiling
 - Use the right KBUILD_MODNAME also when the user just wants a .i/.s/.lst
   file for debugging and also when generating modversions
 - It looks like with your current approach you can't have a ',' or '-' in
   KBUILD_MODNAME - however, that means that KBUILD_MODNAME is not quite
   right for passing module parameters for built-in modules on the command
   line, it would be confusing to pass parameters for ide-cd as
   ide_cd.foo=whatever. So that part could use a little more thought.
 - If you think your module_names trick makes a noticable difference, feel
   free to re-add it.
 - It's possible that objects are linked into more than one module - I
   suppose this shouldn't be a problem, since these objects hopefully
   don't have a module_init() nor do they export symbols. Not sure if your
   patch did handle this.

 - compile fixes in amiflop.c
 - removal of dead local variables in ll_rw_blk.c
 - removed gratitious devfs_get_handle() in usb/input/hiddev.c
   (no need to do lookup for "usb" and then create "hid" in
   there - enough to create "usb/hid" at once).

dasd.c forgot to set ->private_data, but was using it ;-/  Fixed.

Remaining dasd_devmap_from_kdev() callers switched to
dasd_devmap_from_bdev() (other than call from dasd_devmap_from_bdev(),
that is).

dasd_devmap_from_kdev() merged into dasd_devmap_from_bdev().

Eliminated several gratitious ->bd_dev uses.

Bunch of kdevname() uses replaced with bdevname().

__bdevname() switched from kdev_t to dev_t; callers updated.

Compile fixes, cleanup.

RAID autoconfig rewritten to use syscalls and moved into do_mounts.c;
use of devfs_get_handle() in do_mounts.c also rewritten in syscalls.

paride/pseudo.h fed through Lindent, use of timer replaced with
schedule_delayed_work() - that's what the old code tried to emulate.

Instead of user_path_walk() and comparing dentries, sys_swapoff()
opens its argument and compares ->i_mapping.  Result: slightly
simpler code and swapoff(2) becomes tolerant to e.g.

	swapon /dev/sda2
	switch root from initrd to sda1
	....
	swapoff /dev/sda2  # where /dev is from sda1, not from initrd

current tree fails in the case above (different dentries -> no love).

Spotted by Andries - cloning namespace assumes that new tree is
congruent to the old one (when switching root/cwd) but actually
inverts the order of children in each node.

Buffer I/O error on device loop: its use of sendfile is (trivially)
broken - retval is usually count done, only an error when negative.

This code (like the old one) does not correctly handle partial reads.

Nearby spinlocking clearly bogus, delete instead of remarking on it.

This file was somehow skipped (along with jfs_acl.h> when I checked in
the ACL support.

This patch will break some userspace monitoring apps in the name of
having sane disk statistics in 2.6.x.

Patch from Rick Lindsley <ricklind@us.ibm.com>

In 2.5.46, there are now disk statistics being collected twice: once
for gendisk/hd_struct, and once for dkstat.  They are collecting the
same thing.  This patch removes dkstat, which also had the disadvantage
of being limited by DK_MAX_MAJOR and DK_MAX_DISK. (Those #defines are
removed too.)

In addition, this patch removes disk statistics from /proc/stat since
they are now available via sysfs and there seems to have been a general
preference in previous discussions to "clean up" /proc/stat.  Too many
disks being reported in /proc/stat also caused buffer overflows when
trying to print out the data.

The code in led.c from the parisc architecture has not apparently been
recompiled under recent versions of 2.5, since it references
kstat.dk_drive which doesn't exist in later versions.  Accordingly,
I've added an #ifdef 0 and a comment to that code so that it may at
least compile, albeit without one feature -- a step up from its state
now.  If it is preferable to keep the broken code in, that patch may
easily be excised from below.

We're currently incrementing /proc/vmstat:pgalloc in front of the
per-cpu page queues, and incrementing /proc/vmstat:pgfree behind the
per-cpu queues.  So they get out of whack.

Change it so that we increment the counters each time someone requests
a page.  ie: they're both in front of the queues.

Also, remove a duplicated prep_new_page() call and as a consequence,
drop the whole additional list walk in rmqueue_bulk().