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

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

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

This takes advantage of the implicit list ordering of kobjects now present,
and uses list_for_each_entry() for simplicity.

Previously, we would insert kobjects into their kset's lists at different
locations based on if they had a parent or not - We kept an explicit 
depth-first list by placing devices directly before their parents.

However, we don't need strict ordering. Assuming that a subordinate device 
is always added after its parent (true), then by adding them to the end of 
the list, then subordinate objects will always be farther down the list than
their parent objects. We don't need to do anything special..

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

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

into shaggy.austin.ibm.com:/shaggy/bk/jfs-2.5

A while back, the read_inode method was removed in favor of implementing
jfs_iget rather than just iget.  However, since JFS does not implement it's
own get_dentry export_operation, the generic iget can still be called.
Therefore, we do need the read_inode method, so switch back to defining
jfs_read_inode, and use iget rather than jfs_iget.

This fixes bugzilla.kernel.org's bug #796.

Nothing extra in sysfs (yet) but I have left the way open in the driver
to do this.
Provides vid, vrm, fan_input(1-4), fan_min(1-4), pwm(1-3),
pwm_enable(1-3), in_input(0-4), in_min(0-4), in_max(0-4),
temp_input(1-3), temp_min(1-3), temp_max(1-3), alarms.

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

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

Even with the previous fixes, a stress test of rapidly changing speeds in a loop locked
up my test laptop just after a day. Making the errata 5 workaround unconditional
(previously it was only for certain steppings) seems to have cured it. It's now been
running the stress test for nearly two days without a problem.

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

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

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

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

We should set CONFIG_PCI_DOMAINS=y unconditionally on alpha to avoid
ifdefs - jensen has dummy PCI infrastructure anyway.

This fixes an oversight in the reboot code, making some reboot
incantations fail mysteriously.

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

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

Here is a simplified version of the earlier /dev/mem cleanup.  This version
of the patch no longer pretends to support uncached accesses via
read()/write().  Instead, all it does is:

- consolidate much of the ugly code in uncached_access()

- move pgprot_noncached() macro to pgtable.h for i386, m68k, ppc, ppc64,
  and x86_64

- fix the ia64 implementation to use efi_mem_attributes() to determine
  the cacheability of an address

Eventually, we may want to replace the #ifdef CONFIG_IA64 with #ifdef
CONFIG_EFI, but we can do this "on demand", if and when EFI-based x86
machines become more common.

driver initializations

From: Martin Schwidefsky <schwidefsky@de.ibm.com>

The S390 hardware has the interesting characteristic that the storage key
hardware which records a page's pte-dirtiness is also marked dirty when a
page is modified by the disk hardware.

Consequently, reading data from disk makes the page appear to be dirty and
things which were read from disk need to be written back.

Up to now s390 uses a special bit in the pte that is set in mk_pte for the
first user of a page and makes set_pte to clear the storage key.  The problem
is that this is a race condition if two processes want to access the same
page simultaneously.  Then the page count is already > 1 in mk_pte and nobody
will clear the storage key.  It doesn't lead to any data loss because what
happens is that a clean page is considered dirty and is written back to the
disk.  The worst scenario is a read only disk where this results in i/o
errors (but no data loss).

Martin's fix to this is to clear the page's dirty flag in SetPageUptodate().
Which seems a bit kludgey, but I cannot think of a case in which this in
incorrect, inadequate or inappropriate.  So...