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

into kroah.com:/home/greg/linux/BK/pci-hp-2.5

Here's the memory leaks patch for acpiphp_glue.c.

The patch is modeled after your method for creating files for usb. It
makes a single file for pci sysfs files (except for pool, which I haven't
touched yet). It also exposes more pci information to User Space
through sysfs. Finally, it removes the dependence on the proc pci code
for sysfs files.

Fixes problems found by the CHECKER program in the pci hotplug drivers

Moved functions from drivers/hotplug/pci_hotplug_util.c to
drivers/pci/hotplug.c, which is a better place for them.

Relies on sysfs_update_file() to be present in the kernel.

Here is a little patch that remove procfs stuff in pci_hotplug_core.c
Remove /proc entry for pci_hotplug_core.

These were pointed out by "dan carpenter" <error27@email.com>
from his smatch tool.

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

Ok, here's my proposed fix, which appears to work with preempt.  I haven't
tested on non-preempt, nor (obviously since its from me) SMP.  However,
I forsee no problems caused by this change.

release_dev() sets filp->private_data to NULL when the tty layer has
done with the file descriptor.  However, it remains on the tty_files
list until __fput completes.

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

Add "seqlock" infrastructure for doing low-overhead optimistic reader
locks (writer increments a sequence number, reader verifies that no
writers came in during the critical region, and lots of careful memory
barriers to take care of business).

Make xtime/get_jiffies_64() use this new locking.

Trivial patch from Randy Dunlap <rddunlap@osdl.org> removes some useless
error/retval assignments.

Found by inspection of of the x86_64 gettimeofday.

The problem is that the code always records the maximum value
but it is not reset on the next clock tick.  As written, I see it
keeping the maximum number of microseconds since the last clock tick.

The Stanford Checker identified a memory leak in init/do_mounts.c.

This corrects it.

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

Defaulting to building modules together with vmlinux when just doing
"make" or "make all" is only a good choice when "CONFIG_MODULES" is set.

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

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

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

The updates to use 64-bit jiffies broke fs/proc/proc_misc.c for
architectures still using a 100 Hz clocktick (e.g.  UML)

into dell.com:/home/mdomsch/bk/edd/linux-2.5-edd

into dell.com:/home/mdomsch/bk/edd/linux-2.5-edd

This prevents reporting processes as having started in the future, after
32 bit jiffies wrap.

Use 64 bit jiffies for reporting uptime.

Provide a sane way to avoid unneccessary locking on 64 bit platforms,
and a 64 bit analogous to "jiffies_to_clock_t()".