stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: stable@vger.kernel.org
Subject: Re: stable-rc/linux-3.18.y build: 189 builds: 7 failed, 182 passed, 42 errors, 2856 warnings (v3.18.136-133-g0c8638778159)
Date: Thu, 21 Mar 2019 19:47:02 +0100	[thread overview]
Message-ID: <20190321184701.GC16785@kroah.com> (raw)
In-Reply-To: <1291caf8-a639-ef21-1e02-a8a83b2ee132@collabora.com>

On Thu, Mar 21, 2019 at 06:39:17PM +0000, Guillaume Tucker wrote:
> On 21/03/2019 17:48, kernelci.org bot wrote:
> > arc:    arc-linux-gcc (ARCv2 ISA Linux uClibc toolchain 2017.09) 7.1.1 20170710
> > 
> >     allnoconfig: FAIL
> >     fpga_defconfig: FAIL
> >     fpga_noramfs_defconfig: FAIL
> >     tinyconfig: FAIL
> > 
> > mips:    mips-linux-gnu-gcc (Debian 7.3.0-28) 7.3.0
> > 
> >     bigsur_defconfig: FAIL
> >     sb1250_swarm_defconfig: FAIL
> >     sead3micro_defconfig: FAIL
> 
> Is it actually useful to anyone to show these particular build
> failures?  If not we can filter them out in the kernelci.org
> configuration for 3.18.

I asked what was going on here with MIPS, but no one responded back.  I
think something is really broken as the "normal" -rc releases never
generate this error.  So I've just been ignoring them :)

thanks,

greg k-h

      reply	other threads:[~2019-03-21 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 17:48 stable-rc/linux-3.18.y build: 189 builds: 7 failed, 182 passed, 42 errors, 2856 warnings (v3.18.136-133-g0c8638778159) kernelci.org bot
2019-03-21 18:39 ` Guillaume Tucker
2019-03-21 18:47   ` Greg KH [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=20190321184701.GC16785@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=guillaume.tucker@collabora.com \
    --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).