Merging stackprotector/auto-stackprotector-next Merging safe-poison-pointers/auto-safe-poison-pointers-next There is a wiki covering stuff to do with linux-next atĬONFLICT (content): Merge conflict in arch/arm/KconfigĬONFLICT (content): Merge conflict in net/9p/protocol.c
Thanks to Jan Dittmer for adding the linux-next tree to his build tests Status of my local build tests will be atĪdvice about cross compilers/configs that work, we are always open to add Thanks to those who have contributed, and to those who haven't, please do. Linus' tree), more are welcome (even if they are currently empty). We are up to 135 trees (counting Linus' and 18 trees of patches pending for These builds also have CONFIG_ENABLE_WARN_DEPRECATED,ĬONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary.īelow is a summary of the state of the merge. After theįinal fixups (if any), it is also built with powerpc allnoconfig (32 andĦ4 bit), ppc44x_defconfig and allyesconfig (minusĬONFIG_PROFILE_ALL_BRANCHES) and i386, sparc and sparc64 defconfig. Between each merge, the tree was built withĪ ppc64_defconfig for powerpc and an allmodconfig for x86_64. There are also quilt-import.log and merge.log files You can see which trees have been included by looking in the Next/Treesįile in the source. You should use "git fetch" as mentioned in the FAQ on the wiki To do so as that will try to merge the new linux-next release with the Git:///pub/scm/linux/kernel/git/sfr/linux-next.gitĪre tracking the linux-next tree using git, you should not use "git pull" I have created today's linux-next tree at The kmemleak tree gained a conflict against the x86 tree. The vfs tree gained a build failure so I used the version from 9:10 ` Christian Borntraeger 0 siblings, 1 reply 19+ messages in threadįrom: Stephen Rothwell 7:19 UTC ( / raw)
Msm download tool param preload archive#
Linux-next: Tree for May 7 LKML Archive on help / color / mirror / Atom feed * linux-next: Tree for May 7 7:19 Stephen Rothwell