Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1542026
| From | Paul Gortmaker <paul.gortmaker@windriver.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: Tree for Dec 14 |
| Date | 2016-12-14 17:30 +0100 |
| Message-ID | <sOkBj-cI-5@gated-at.bofh.it> (permalink) |
| References | <sO9mx-1PC-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Dec 13, 2016 at 11:22 PM, Stephen Rothwell <sfr@canb.auug.org.au> 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@de.ibm.com>
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
[...]
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next: Tree for Dec 14 Stephen Rothwell <sfr@canb.auug.org.au> - 2016-12-14 05:30 +0100
Re: linux-next: Tree for Dec 14 Paul Gortmaker <paul.gortmaker@windriver.com> - 2016-12-14 17:30 +0100
Re: linux-next: Tree for Dec 14 Heiko Carstens <heiko.carstens@de.ibm.com> - 2016-12-14 21:10 +0100
csiph-web