Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
	kernel-build-reports@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v3.18.43 build: 8 failures 256 warnings (v3.18.43)
Date: Sun, 23 Oct 2016 00:31:28 +0100	[thread overview]
Message-ID: <20161022233128.GT10208@sirena.org.uk> (raw)
In-Reply-To: <3499554.09WHdqWKVx@wuerfel>

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

On Sat, Oct 22, 2016 at 10:53:20PM +0200, Arnd Bergmann wrote:

> What happened here? There was a successful build for the same commit last
> week, now everything seems broken. Is this still the disk-full problem
> you mentioned in another mail?

Yes, it's the disk full working itself out.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2016-10-22 23:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22  0:53 v3.18.43 build: 8 failures 256 warnings (v3.18.43) Build bot for Mark Brown
2016-10-22 20:53 ` Arnd Bergmann
2016-10-22 23:31   ` Mark Brown [this message]

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=20161022233128.GT10208@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=arnd@arndb.de \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=stable@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox