stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Build bot for Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
	linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v4.9.95 build: 11 failures 0 warnings (v4.9.95)
Date: Fri, 20 Apr 2018 08:46:36 +0200	[thread overview]
Message-ID: <20180420064636.GA4009@kroah.com> (raw)
In-Reply-To: <E1f9PjL-0007vL-9K@optimist>

On Fri, Apr 20, 2018 at 07:41:11AM +0100, Build bot for Mark Brown wrote:
> Tree/Branch: v4.9.95
> Git describe: v4.9.95
> Commit: eedaf21fb3 Linux 4.9.95
> 
> Build Time: 0 min 26 sec
> 
> Passed:    0 / 11   (  0.00 %)
> Failed:   11 / 11   (100.00 %)

These are "fun" to read :(

  reply	other threads:[~2018-04-20  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20  6:41 v4.9.95 build: 11 failures 0 warnings (v4.9.95) Build bot for Mark Brown
2018-04-20  6:46 ` Greg KH [this message]
2018-04-20 11:43   ` Mark Brown

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=20180420064636.GA4009@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).