Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot autobuild we access
Date: Wed, 13 Jul 2016 16:33:31 +0200	[thread overview]
Message-ID: <20160713163331.310524dc@free-electrons.com> (raw)
In-Reply-To: <1468418534.19768.60.camel@synopsys.com>

Hello,

On Wed, 13 Jul 2016 14:02:14 +0000, Vlad Zakharov wrote:

> Unfortunately we still have to much failures for our ARC
> architecture, so we have a lot of urgent work.

Sure, understood.

> Despite this I will try to improve that when I find some free time.

I never found the problem to be sufficiently annoying to have me spend
some time on it. I typically look at the daily reports by e-mail, or
instead write down the autobuild.buildroot.org manually.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-07-13 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 13:38 [Buildroot] buildroot autobuild we access Vlad Zakharov
2016-07-13 13:52 ` Thomas Petazzoni
2016-07-13 14:02   ` Vlad Zakharov
2016-07-13 14:33     ` Thomas Petazzoni [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=20160713163331.310524dc@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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