- Created arch/i386/kernel/acpi/
- Split file into boot.c and sleep.c.
- Moved acpi_wakeup.S into there.

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

When ACPI turns the system off on shutdown, it actually enters S5, a sleep
state. This functionality is dependent on CONFIG_ACPI_SLEEP, which is 
dependent on CONFIG_SOFTWARE_SUSPEND.

This patch breaks the power off functionality into a separate file, and 
removes the dependency on the above-mentioned crap. Finally, power off works
for me again. 

Thanks to Tobias Ringstrom for the original patch.

Each power management scheme was implmenting a sysrq callback for 'o' which
would call their respective power off routines. 

This moves the installation of the sysrq handler to kernel/pm.c, and calls
pm_power_off(), which will work for any platform that has that method
defined. 

Recently, the acpi proc files were changed to use the seq_file interface.
As a result of this, the write methods became top-level write() methods
(i.e. not called by the proc layer). 

Whoever made these changes, did not take into account that the parameters 
passed to these changed. The fourth parameter previously was a void*, that
pointed to the private data for the owner of the file, and some of the 
methods still expected this, even though the parameter is now an loff_t*,
and points to the offset into the file that is being written. Huge Bug. 

This fixes the broken methods to look in the same place as the other 
methods (i.e. in the file's private data).
 

- Check if __linux__ is defined in include/acpi/platform/acenv.h, instead
  of -D_LINUX (defined by drivers/acpi/Makefile).
- Remove -D_LINUX from custom CFLAGS.
- Remove include path of include/acpi, since all headers are looked for in
  include/acpi.

- Prevent users from screwing themselves by removing support for entering
  S5 from the proc file. S5 is 'soft-off' and the state the system enters
  when powering down. It needs to be preceded by a proper shutdown sequence
  and should not be triggered manually. 
- Fix a potential unchecked array reference using the written value as the
  index.

My printf manpage says:

       z      A  following  integer  conversion  corresponds to a
              size_t or ssize_t argument. (Linux libc5 has Z with
              this meaning. Don't use it.)

And the opengroup spec says

z Specifies that a following d , i , o , u , x , or X conversion specifier
  applies to a size_t or the corresponding signed integer type argument; or
  that a following n conversion specifier applies to a pointer to a signed
  integer type corresponding to a size_t argument.


yet our vsnprintf implementation has

				/* 'z' support added 23/7/1999 S.H.    */
				/* 'z' changed to 'Z' --davidm 1/25/99 */


I guess the path of least surprise is to support both.  gcc-3.2.1 doesn't
  seem to care.

The return type of sizeof() is size_t.  On many architectrues size_t is
unsigned long, and may not be printed with %d.  Use %Zu instead.

Need to reenable interrupts around the call to scsi_register(), which blocks.

An anonymous fixed mmap with CONFIG_HUGETLB_PAGE=y will dereference NULL.  We
recur into the pagefault handler with mmap_sem held and lock up.

Patch from Davide Libenzi <davidel@xmailserver.org>

Changes :
 - Timeout overflow check
 - Ceil()ing of ms->jif conversion
 - Syscalls return type int->long

Patch from: Peter Waechtler <pwaechtler@mac.com>

Addresses BUGME bug #331.  "OSS CS4232 nasty spinlock printks on boot"

The locking in some OSS modules is really lousy.
Because save_flags/cli/restore_flags could be used recursivly - the
programmers pushed the locking too far the lower level.

Because on ISA cards the register sets are usually multiplexed
you had to write to an address latch and then access the data port
in an "atomic" manner.

I suggest removing the locking from ad_read/ad_write +
ad_{enter|leave}_MCE and clamping the locks wherever the functions
are called. I hope the attached patch does that correctly.

Yes, I don't like all the timeout loops while holding the locks:
high chances that a cpu is spinning in interrupt context :(

Patch from: David Mosberger <davidm@napali.hpl.hp.com>

Please remember to declare the return-type of syscall stubs as "long".
On 64-bit platforms, it's generally necessary to ensure that the
entire 64-bit return value is valid (and can be checked against
negative values).

Patch from: Frank Davis <fdavis@si.rr.com>

The following addresses bugzilla bug # 340.

Patch from: Frank Davis <fdavis@si.rr.com>

The following patch addresses bugzilla bug # 341.

Patch from: john stultz <johnstul@us.ibm.com>

This patch simply fixes the summit subarch to allow summit kernels to
boot on normal systems.

Someone typed `config' when they meant `conf'.

Also fix a function-defined-but-not-used warning.

This driver is calling down into scsi_register with local interrupts
disabled.  scsi_register performs blocking allocations, starts kernel
threads, etc.  slab debugging gets offended by someone performing blocking
operations with local interrupts disabled.

Patch from Tim Schmielau <tim@physik3.uni-rostock.de>

Converts many open-coded jiffy comparisons to use time_after/before/etc.

Patch from Dipankar Sarma <dipankar@in.ibm.com>

All fs should be using dcache APIs to manipulate dcache hash lists.  This is
in line with the dcache cleanup patch (dcache_rcu-1) from Maneesh that Linus
accepted.  This seems like a reasonable cleanup.  One change though, we don't
need to grab dcache_lock while deleting dentries from the private list and
__d_drop() should suffice here.

make the adaptec driver compile

Patch from Rik van Riel <riel@conectiva.com.br>

the following patch, against today's BK tree, fixes a small
SMP race in disassociate_ctty.  This function gets called
from do_exit, without the BKL held.

However, it sets the *tty variable before grabbing the bkl,
then makes decisions on what the variable was set to before
the lock was grabbed, despite the fact that another process
could modify its ->tty pointer in this same function.

Patch from Oleg Drokin <green@namesys.com>, Nikita Danilov <Nikita@Namesys.COM>

There is no uniprocessor definition of _raw_write_trylock(), so
write_trylock() doesn't work on UP.

kdev_t.value is not an int.  Code looks fishy.