LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 24
Date: Mon, 28 May 2018 11:08:22 +0200	[thread overview]
Message-ID: <CAK8P3a2vmbxYmMqTYb0kHoB3uTcWi_=hL=Wunfw6nqE0NGr+QA@mail.gmail.com> (raw)
In-Reply-To: <20180527184639.GD1564@sirena.org.uk>

On Sun, May 27, 2018 at 8:46 PM, Mark Brown <broonie@kernel.org> wrote:
> On Fri, May 25, 2018 at 06:30:25PM +0100, Mark Brown wrote:
>
>> quickly as hoped, sorry.  There should be another linux-next done by me
>> for today (25th) as well, that will appear tomorrow all being well.
>
> There won't be.  For some reason I need to get to the bottom of the
> builds are taking a lot longer than they have previously which has
> caused a whole bunch of problems.
>
>> Stephen should be back on Monday.

One possible reason for slowdown on ARM allmodconfig might be the addition of
KCOV, though that is only enabled in mmotm at the end of your builds.

       Arnd

  parent reply	other threads:[~2018-05-28  9:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 17:30 Mark Brown
2018-05-27 18:46 ` Mark Brown
2018-05-27 19:20   ` Stephen Rothwell
2018-05-28  9:08   ` Arnd Bergmann [this message]
2018-05-28 11:04     ` Mark Brown
2018-05-28 12:23 ` Andy Shevchenko
2018-05-29 10:38   ` Mark Brown
2018-05-29 11:18     ` Stephen Rothwell
2018-05-29 11:37       ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2022-05-24  9:26 Stephen Rothwell
2021-05-24  6:08 Stephen Rothwell
2019-05-24  4:07 Stephen Rothwell
2017-05-24  3:23 Stephen Rothwell
2016-05-24  2:43 Stephen Rothwell
2012-05-24  6:49 Stephen Rothwell
2011-05-24  4:02 Stephen Rothwell
2010-05-24  3:57 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='CAK8P3a2vmbxYmMqTYb0kHoB3uTcWi_=hL=Wunfw6nqE0NGr+QA@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: Tree for May 24' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).