Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-14
Date: Tue, 15 Mar 2016 12:26:36 +0000	[thread overview]
Message-ID: <56E7FF7C.7020100@imgtec.com> (raw)
In-Reply-To: <20160315073022.B57511011CC@stock.ovh.net>

Hello Peter and Thomas,

On 15/03/16 07:30, Thomas Petazzoni wrote:
> Build statistics for 2016-03-14

[...]

>       mipsel |                     mosh-1.2.5 | NOK | http://autobuild.buildroot.net/results/e0a130e8a43b92b10584435b8e0088f8e77a2691/

This one should be automatically fixed when this patch gets applied:

http://patchwork.ozlabs.org/patch/594919/

We have just released a new version of Buildroot and started a new
development cycle for the next release. I think it's a good moment to
apply a patch like that one so we will have plenty of time to fix the
problems that it may cause.

Regards,

Vincent.

      reply	other threads:[~2016-03-15 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-14 Thomas Petazzoni
2016-03-15 12:26 ` Vicente Olivert Riera [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=56E7FF7C.7020100@imgtec.com \
    --to=vincent.riera@imgtec.com \
    --cc=buildroot@busybox.net \
    /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