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

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

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

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-core

the top of the kernel stack space before entering userland.

 Kay Sievers tried with his ~500kB firmware image and kmalloc was not
 capable of getting that much memory. He suggested using vmalloc which
 sound reasonable.

Made variables static that were global, and cleaned up some sparse warnings.

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-core

This patch converts the file to C99 initializers. The patch is against
the current BK. The patch is untested as I don't have access to an Alpha
machine.

Art Haas

The oprofile_arch_exit() in discarded .exit.text section is being
called from oprofile_init() in retained .init.text section.
This causes final link failure with oprofile compiled in.

Ivan.

Add missing tty_set_operations().

Ivan.

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

In some cases, we're reading the wrong bits for large tags.  This patch corrects
the issue by setting the affected bits forward by an offset of 2 (skipping over
the size portion of the tag).

Must have missed it earlier, but the pci module parameter is not needed.

The irq index is used instead of the dma index when parsing dmas.

This patch adds the "get" command because at this point it is needed
for debugging.

If a device is disabled when initially read, its blank resource data will not
be cleared and the pnp layer will assume incorrectly that the device has
already been configured.  This patch resolves the issue by initializing the
resource table if the device is found to be disabled.

Fixes a trivial typo in an export symbol macro.

This patch resolves the compiler warning caused by the depreciated check_region
function.  It may not be the best solution but check_region really is what is
needed here because we never actually have to call "request_region".  If prefered,
I could alternatively request and release but doing so would be less efficient.

This patch does the following...
1.) changes struct pnp_resources to pnp_option for clarity
2.) greatly cleans up resource option registration
3.) removes some of the current conflict prevention code in
order to increase flexibility, (users will have more control)
4.) various manager cleanups, resulting code is more efficient
5.) fixes the locking bugs many have reported (now uses a mutex)
6.) removes the conflict displaying interface
 - it is better to handle such things in user space
7.) also many misc. cleanups

Make sure that the ipc_head list cannot change under us by
protecting it with a spin lock.

replace the somewhat weird open-coded doubly-linked list with
a <linux/list.h> list.

Remove MOD_{INC,DEC}_USE_COUNT and introduce .owner instead.

The tty changes introduced some typos. These are now fixed, this
doesn't really address probably still existing races, though.

This adds a separate SERIAL_8250_ACPI config option and makes the
8250_acpi.c code dependent on ACPI_BUS (since acpi_bus_register_driver()
is a prerequisite).

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn

into kernel.bkbits.net:/home/davem/net-2.5

into nuts.ninka.net:/home/davem/src/BK/net-2.5

I don't understand what was on the mind of Procom programmers,
why do all this inverted logic? Its plain confusing, revert it.
Thanks to DaveM for asking if the logic was inverted, I should
have killed this weird stuff a long time ago :-\

With this we make it easier to write correct network families as less
details need to be taken into account, as well in the current state we
make the non-refcounting protocols (the ones still keeping deliver_to_old_ones
in the tree) suck less. 8)

Left a WARN_ON in sk_del_node_init for a while, so that we can catch cases
where we're using __sock_put on a struct sock that has refcnt == 1, which
is not the case for all the ones I tested.

into nuts.ninka.net:/home/davem/src/BK/net-2.5