All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 14
Date: Wed, 14 Dec 2016 21:07:51 +0100	[thread overview]
Message-ID: <20161214200751.GA3622@osiris> (raw)
In-Reply-To: <CAP=VYLqtuDk-wyHqrp8kySo6Uz4=5QQ_P5qweW_g9W9QkYmzmg@mail.gmail.com>

On Wed, Dec 14, 2016 at 11:25:49AM -0500, Paul Gortmaker wrote:
> 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.

Yes, a fix is ready to be merged soon:

https://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h=features&id=75a357341e7c9d3893405ea6f9d722036012dd1f

Thanks,
Heiko

  reply	other threads:[~2016-12-14 20:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14  4:22 linux-next: Tree for Dec 14 Stephen Rothwell
2016-12-14 16:25 ` Paul Gortmaker
2016-12-14 20:07   ` Heiko Carstens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-14  5:33 Stephen Rothwell
2022-12-14  3:21 Stephen Rothwell
2021-12-14 22:32 broonie
2021-12-15  0:37 ` Nathan Chancellor
2021-12-15 15:54 ` Andy Shevchenko
2021-12-15 18:06   ` Mark Brown
2021-12-15 18:40     ` Andy Shevchenko
2021-12-15 18:43       ` Mark Brown
2020-12-14 10:20 Stephen Rothwell
2018-12-14  7:18 Stephen Rothwell
2018-12-15 15:51 ` Guenter Roeck
2017-12-14  7:06 Stephen Rothwell
2015-12-14  6:18 Stephen Rothwell
2012-12-14  7:42 Stephen Rothwell
2012-12-14  7:42 ` Stephen Rothwell
2011-12-14  7:26 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161214200751.GA3622@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=oberpar@linux.vnet.ibm.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.