Current gcc requires that both the declaration and the definition of
functions describe the same register conventions.

into intel.com:/home/lenb/src/linux-acpi-test-2.6.4

  http://bugzilla.kernel.org/show_bug.cgi?id=1669

into intel.com:/home/lenb/src/linux-acpi-test-2.6.4

This fixes a typo in the list of PCI IDs in radeonfb, which in turn
fixes detection of some mobility models.

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

Patch from Deepak Saxena

The ARM makefile currently assumes that the compiler being used 
defaults to little-endian builds unless the big-endian options
are provided. This may not always be the case (my toolchains default
to BE since that's what I mostly work with) so this patch forces
endianess options to be passed to the toolchain. W/O this,
building without CONFIG_CPU_BIG_ENDIAN on a big-endian toolchain 
will still result in a big-endian kernel.

Patch from Ian Campbell

__arch_strncpy_from_user needs to be exported if you build the
framebuffer console driver as a module. 

Patch from Deepak Saxena

 - inode leak on d_alloc_root() failure

 - inode leak on d_alloc_root() failure
 - sanitized the cleanup logics

 - inode leak on d_alloc_root() failure

 - inode leak on d_alloc_root() failure

 - inode leak on d_alloc_root() failure

 - inode leak on d_alloc_root() failure

 - inode leak on d_alloc_root() failure

 - inode leak on d_alloc_root() failure

 - inode leak on d_alloc_root() failure
 - unchecked result of d_alloc_root() leading to oops in fs/super.c

 - unchecked result of d_alloc_root() leading to oops in fs/super.c

 - inode leak if d_alloc_root() fails.

 - oops if inode allocation fails.

 - useless dput(NULL) on failure exit (would be a double-free if
   we ever got there with non-NULL dentry).

 - leak of root inode if d_alloc_root() fails.

gatgetfs fill_super:
 - double-free of inode on last two failure exits
 - leak on the last failure exit
 - touching addresses near 0 on last two failure exits

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

New revision of the Sigmatel irda driver.  This version has much
better performance and doesn't drop frames in FIR mode.
Tested with both UHCI and EHCI/OHCI against nsc-ircc on laptop.
Thanks to Martin for additional testing and feedback.

* Receiver:
	- changed from interrupt to bulk URB.  Queue's one bulk
	  urb per USB tick (1ms).
	- FIR unpack now uses get_unaligned and cpu32_le
	  instead of explicit shifts
	- FIR unpack copies small frames
* Transmitter:
	- pack data into io buffer.  Since irda is half duplex
	  can use same buffer for transmit and receive.
	- use xchange and wait_event for synchronization
* Other:
	- use USB format messages rather than IRDA (ugly)
	- clean up USB startup
	- reset device on network open to clear up stuck state
	- handle FIFO errors
	- disconnect cleanup (from viro)
	- don't DMA onto stack when reading fifo status

into nuts.davemloft.net:/disk1/BK/sparc-2.6

into intel.com:/home/lenb/src/linux-acpi-test-2.6.4

It was missing an "s" from "uses_dvo"

This adds a "timbase" entry in /proc/cpuinfo like p/iSeries that
provides the CPU timebase frequency.  It is using by a all sort of
performance analysis tools we are hacking in house.

It also remove a useless bit about the l2 cache that was copied over
from ppc32.

I've had reports of flicker that appear with large (23") flat panels
and radeonfb. From experiments, it appears that forbiding the "odd"
PLL divider values fix it (like it fixes the blur problem on TMDS2).

There should not be anything special with TMDS1 and "odd" PLL values
though, so the problem may be subtly different (a bandwidth problem),
but until I have proper bandwidth calculation and access to this
monitor, the following patch is an acceptable workaround (Odd PLL values
aren't that useful anyway)

This fixes the permedia2 framebuffer driver to the new API.

[ Currently it doesn't even compile.  This only touches the current
  permedia driver.  ]

into hostme.bitkeeper.com:/repos/j/jfs/linux-2.5

* Tidy up some of the arguments to iommu_*()
* Comment cleanup
* Don't bump the hint to the next block for large allocs, to avoid
  fragmentation.
* Simplify vmerge logic during SG allocations
* Move the memory barriers from the bus-specific parts into the common
  code.

Some changes are mine, some are from Ben Herrenschmidt.

- fix bug introduced by my recent fixes
  (do not try to disable 66MHz clock on PDC20246)
- cleanup cable verification code a bit
- remove unused macros (leftovers from driver split-up)
  and duplicated define from pdc202xx_old.h