As the merge window is open, please do not add 2.6.37 material to yourlinux-next included trees until after 2.6.36-rc1.

Changes since 20100806:

The s5p tree lost a conflict.

The mips tree lost its conflicts.

The genesis tree lost its conflict.

The cifs tree lost its build failure.

The mtd tree gained a conflict against Linus' tree.

The block tree lost its conflict.

The kgdb tree gained a conflict against Linus' tree and a build failureso I used the version from next-20100806.

The tip tree lost its conflicts.

The staging-next tree lost its conflicts.

----------------------------------------------------------------------------I have created today's linux-next tree atgit://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git(patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ). If youare tracking the linux-next tree using git, you should not use "git pull"to do so as that will try to merge the new linux-next release with theold one. You should use "git fetch" as mentioned in the FAQ on the wiki(see below).

You can see which trees have been included by looking in the Next/Treesfile in the source. There are also quilt-import.log and merge.log filesin the Next directory. Between each merge, the tree was built witha ppc64_defconfig for powerpc and an allmodconfig for x86_64. After thefinal fixups (if any), it is also built with powerpc allnoconfig (32 and64 bit), ppc44x_defconfig and allyesconfig (minusCONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparcand sparc64 defconfig. These builds also haveCONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK andCONFIG_DEBUG_INFO disabled when necessary.

Below is a summary of the state of the merge.

We are up to 169 trees (counting Linus' and 22 trees of patches pendingfor Linus' tree), more are welcome (even if they are currently empty).Thanks to those who have contributed, and to those who haven't, please do.

Status of my local build tests will be athttp://kisskb.ellerman.id.au/linux-next . If maintainers want to giveadvice about cross compilers/configs that work, we are always open to addmore builds.