On Tue, Dec 13, 2016 at 11:22 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi all, > > Please do not add any material for v4.11 to your linux-next included > branches until after v4.10-rc1 has been released. > > Changes since 20161213: > > The vfs-miklos tree gained a conflict against the ubifs tree. > > The akpm-current tree gained a conflict against the jc_docs tree. > > Non-merge commits (relative to Linus' tree): 4498 > 4320 files changed, 189429 insertions(+), 94239 deletions(-) New s390 build failure today: http://kisskb.ellerman.id.au/kisskb/buildresult/12883922/ I reproduced it locally using the older korg s390 toolchain. Reverting this and the file compiles fine: commit d543a106f96d6f15e4507cf349128912d44356d9 Author: Heiko Carstens <heiko.carstens@xxxxxxxxxx> Date: Tue Dec 6 15:52:10 2016 +0100 s390: fix initrd corruptions with gcov/kcov instrumented kernels Appears old toolchains don't like this commit. Paul. -- > > ---------------------------------------------------------------------------- > > I have created today's linux-next tree at > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > (patches at http://www.kernel.org/pub/linux/kernel/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" and checkout or reset to the new > master. > > 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 (with > CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a > native build of tools/perf. After the final fixups (if any), I do an > x86_64 modules_install followed by builds for x86_64 allnoconfig, > powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig [...] -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
