Hi all,
Changes since next-20080502:
New tree: v9fs.
The v4l/dvb breakage still required a small patch but the div64_64 to
div64_u64 rename breakage was fixed.
The kbuild tree was dropped due to build errors (notified).
The vfs tree linux/file.h splitup failure was fixed.
Conflicts continue to disappear due to code being merged upstream. Also
several minor/whitespace conflicts have turned up due to merging slightly
different versions of patches than what is in the linux-next tree.
The s390 build breakage was fixed.
I have applied a fix for the dev_name introduction breaking edac
(notified with patch).
I am still carrying two PNP fixup patches.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(tar balls 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 merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups, it is also built with powerpc allnoconfig,
44x/ebony_defconfig and allyesconfig.
Below is a summary of the state of the merge.
We are up to 68 trees (counting Linus' and 9 trees of patches pending for
Linus' tree (which are mostly empty)), 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 at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, w...
