Hi all,
Changes since next-20080905:
New tree: pxa
The arm tree lost its 4 conflicts.
The parisc tree gained a conflict against the dwmw2 tree.
The pxa tree gained a conflict against the arm tree and required a build
fix patch.
The sparc tree lost its conflict.
The x86 tree lost a conflict but gained a conflict against each of Linus'
tree and the pci-current tree and required a build fix patch.
The driver-core tree gained a build fix patch.
The tip-core tree gained a patch to eliminate a build warning.
The cpus4096 tree gained a conflict against the x86 tree.
The ftrace tree lost a build warning patch.
The timers tree gained a conflict against each of the x86 and pci-current
trees.
The kvm tree gained a conflict against the timers tree.
The rr tree gained conflicts against the driver-core and ftrace trees but
lost a build fix patch.
The block tree lost 2 conflicts.
The oprofile tree gained a conflict against the timers tree but also lost
a conflict.
The sparseirq tree lost its 4 conflicts.
I have also applied the following patches for known problems:
revert BUILD_BUG_ON change
sparc: qlogicpti fallout from sbus removal
fix IXGBE dependencies
Revert "lockdep: fix compilation when CONFIG_TRACE_IRQFLAGS_SUPPORT
is not set"
net: ip_vs_proto_tcp build fix
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
are 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 the
old 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/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each ...