- Wrap unused function in same #ifdef as caller.
- Boggle as to WTF CONFIG_MOUNT_ROOT_FAILED_MSG is supposed to do.

A recent slew of ACPI "fixes" completely broke the build when one built 
without SMP, IO APICs, or Local APICs. 

Bad Intel, no cookie.

Hyperthreading is a Pentium 4-specific feature. It should only depend on 
whether the user has configured P4 support in. 

- Add prototypes for split-up swsusp functions that can be called from PM
  core: 

  save()
  write()
  read()
  restore()
  free()

- Base PM core algorithm on existence of these functions, and allow 
  graceful failure at each step. 

- Add pm_resume() function to be called on init to attempt to read swsusp
  image. 

- Add debugging. 

- Make sure we can handle all modes for suspend-to-disk.

- Add empty split-up functions to swsusp. 

Suspend-to-disk can be handled in numerous ways, some we have control over,
and others we don't. The biggest difference is whether or not the firmware
is responsible for entering a low-power state or if the platform driver is.
The two modes are incompatible, so we enable the platform driver tell the 
PM core when they register their pm_ops (via the ->pm_disk_mode) field. 

If the firmware is responsible, then it will also write memory to disk, 
while the kernel is otherwise responsible. However, a user may choose to 
use the in-kernel suspend mechanism, even if the system supports only 
the firmware mechanism. Instead of entering a low-power state, the system
will turn off (or reboot for testing). 

A sysfs file -- /sys/power/disk -- is available to set the mode to one of:

  'firmware' 
  'platform'
  'shutdown'
  'reboot'

The latter two are settable any time, and assume that one is using swsusp. 
The other two are only settable to what the platform supports.

This removes EXPORT_SYMBOL(add_timer) since add_timer() became inline
recently.

into home.osdl.org:/home/torvalds/v2.5/linux

We know we have the right version because we were compiled in the
same kernel tree..

into home.osdl.org:/home/torvalds/v2.5/linux

into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk

This change seems to have been missed for some time.  Remove
__dump_stack(), and convert show_trace_task() to show_stack().

ARM had CONFIG_DEBUG_INFO for ages.  Unfortunately, the new
CONFIG_DEBUG_INFO was rather blindly applied across all architectures.
This removes the duplication from the ARM architecture.

into home.osdl.org:/home/torvalds/v2.5/linux

recent cleanups (removal of link release timer and
the STALE_CONFIG crud).

Yeah, it sucks for now. But, we'll get it right eventually. 

- Define and fill acpi_pm_ops, and register it on startup with the PM core.

- Fill methods with only ACPI-specific code, leaving device power down, etc
  up to the PM core. 

Use /sys/power/state instead. 

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

This updates the blkmtd driver with the latest which has been in the MTD
CVS for quite a while.  It is a rewrite from the 2.4 version to work
with the new block layer changes.

When the *config targets were moved to scripts/kconfig/Makefile
the graphical configurator support broke.

The following patch is a minimal fix, required to restore support
of 'make xconfig' and 'make gconfig'.

A small bug in local.h apparently got copied a few times.
I noticed this because I copied the same bug to s390.
This patch should fix the occurrences in BK, but there
are others that are not merged yet, e.g. ppc64 in -mm3.

This is a rewrite of the awe_wave detection code that will allow this
driver to be compiled.  It moves detection functions to a common
location at the end of the file and makes the code driver-model
compatible.  Also it fixes a bug in which the driver could possibly
write to incorrect ports when using isapnp cards.

Unfortunantly I do not currently have an AWE32 to test these changes so
I could only check for compilation and driver registration.

There was a quite nasty long standing bug in the x86-64 port.  The
interrupt gates had a DPL of 3, allowing user space to trigger any
interrupt.  I have not found a way to exploit it this to crash the
kernel, but it definitely shouldn't happen.  It could e.g.  cause
problems with drivers that do not handle shared interrupt properly.

This also broke some programs who assumed that int <random number>
causes a signal.

Various compile fixes for x86-64 in the current BKCVS tree.

- Use new information from acpi_pci_link_get_irq: handle 
  edge and level triggered interrupts properly
- Fixes for pci_dev->pretty_name 

Only changes x86-64 specific code.

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

Linux historically has had. Only x86-64 uses anything else, so
make the special case be _there_.

- Don't leave resource name uninitialized if CONFIG_EISA_NAME is not set.
- Print root device bus_id (so we know which bridge is probed).
- From Zwane Mwaikambo : Add a release method to virtual root, so it
  stays quiet if probing fails (because some pci-eisa bridge have been
  found before).

From: Mark Hemment <markhe@veritas.com>

  For RPC over UDP, after receiving a packet kick another thread as soon
as possible.  This helps NFS performance.

This is important on multi-homes hosts.

Just make sure that once SK_DEAD is set, nothing is attempted on the socket.

From: Bernardo Innocenti <bernie@develer.com>

sysctl.h needs compiler.h

Fix infinite loop in the device probe function.

From: Peter Osterlund <petero2@telia.com>

It oopses on module unload in the kobject layer due to misordered destruction
of things.

And we need to initialise the unplug timer in blk_alloc_queue(), because we
kill that timer in blk_alloc_queue()'s companion function,
blk_cleanup_queue().

From: Philippe Elie <phil.el@wanadoo.fr>

If drain_array_locked() is passed the `force' command, it must go in and
empty the head array.