The following patches should fix those last two issues - compiling boot.c
for UP and compiling proc.c by default.

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

  This is needed because mark_buffer_dirty is now checking if buffer is up to date.
  Noticed by Alex Tomas <bzzz@tmi.comex.ru>

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

into tetrachloride.(none):/mnt/stuff/kernel/2.5/cpufreq

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

into tetrachloride.(none):/mnt/stuff/kernel/2.5/cpufreq

into tetrachloride.(none):/mnt/stuff/kernel/2.5/cpufreq

This should fix the x1.0 multiplier bug (should be x10.0)
Spotted by Dominik Brodowski

If you have !CONFIG_ACPI_SLEEP and CONFIG_PROC_FS, drivers/acpi/sleep/proc.o
is built, but drivers/acpi/sleep/main.o is not.

But proc.o needs symbols from main.o

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

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

This problem was identified by Olaf Kirch:

In xprt_request_init(), the XID allocation needs to be protected by a
global spinlock.

 - Only set up pipefs entries for those RPC services that actually
   need them (for the moment NFS only). Portmap, lockd,... shouldn't
   need to make upcalls.

 - Add in missing semaphore in rpc_populate().

 - Make inode/dentry variable names in rpc_depopulate/rpc_populate
   more consistent w.r.t other functions in rpc_pipe.c

 - Call shrink_dcache_parent() in order to clean up child entries
   before we rmdir().

This patch fix es the signals vs strace problem.  The signal code
assumes that anybody who is TAK_STOPPED will check signals before
resuming, and the ptrace paths didn't do that.

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

This is a rather large update for the starfire network driver,
implementing VLAN support, 64-bit dma_addr_t support, and NAPI support. It
also fixes a couple of show-stopper bugs in the old driver which were
biting real people out there.

I've had a few positive test results with this version, including one from
Martin Bligh who tested it on his monster SMP boxes. So I'm pretty
confident that it's mostly all right, and certainly better than what's
currently in the tree.

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

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

- It depends on the rest of the subsys_initcalls in acpi to be done to get
  the sleep info from the firmware. 
- It doesn't need to be available any earlier...

- Make acpi_sleep_proc_init() a late_initcall(), and not called from 
  acpi_sleep_init(). This guarantees that the acpi proc hierarchy is at 
  least there when we create the dang file.

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

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

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

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

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

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

This converts the driver to use the new scsi_add_host() interface to add
scsi controllers.

This removes the old LinuxVersionCode() and replaces it with
KERNEL_VERSION().  Thanks go to Adrian Bunk for sending the initial
version.

This adds a few bits of code and couple #ifdefs that are needed to
enable this driver to work for 2.4 as well as 2.5.

This adds back the reboot_notifier hook that was accidentally removed in
the last set of patches.

It also adds support handle a Mode Page 8 command so the scsi layer
won't complain anymore.  And the movement to using ->device to get scsi
numbers resulted in 2 typos in debug code.  These are also fixed.

Lingering around for a while. 2.4 forward port.