From: Mark Brown <broonie@kernel•org>
To: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org
Subject: Re: next-20160201 build: 1 failures 25 warnings (next-20160201)
Date: Mon, 1 Feb 2016 17:28:31 +0000 [thread overview]
Message-ID: <20160201172831.GE4455@sirena.org.uk> (raw)
In-Reply-To: <E1aQHbv-0001K4-HG@optimist>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
On Mon, Feb 01, 2016 at 04:45:57PM +0000, Build bot for Mark Brown wrote:
> Tree/Branch: next-20160201
> Git describe: next-20160201
> Commit: 99e832465a Add linux-next specific files for 20160201
>
> Build Time: 187 min 35 sec
The failures here were false positives caused by an issue with the
environment I believe, things should be fine for future builds.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
parent reply other threads:[~2016-02-01 17:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1aQHbv-0001K4-HG@optimist>]
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=20160201172831.GE4455@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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