From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] travis-ci: Try harder to build all ARM targets
Date: Sun, 6 Nov 2016 20:17:57 -0500 [thread overview]
Message-ID: <20161107011757.GO20830@bill-the-cat> (raw)
In-Reply-To: <1478388889-26646-1-git-send-email-trini@konsulko.com>
On Sat, Nov 05, 2016 at 07:34:49PM -0400, Tom Rini wrote:
> The way that we have things broken down currently allows for some
> combinations of vendor or CPU to not be built. To fix this, create a
> new catch-all job that excludes everything we've built elsewhere. For
> the sake of simplicity we are allowing for the possibility of some
> overlap between the vendor-based jobs and the CPU-based jobs. While
> we're in here, make a failed build provide the summary of failure.
>
> Signed-off-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161106/f27341d3/attachment.sig>
prev parent reply other threads:[~2016-11-07 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 23:34 [U-Boot] [PATCH] travis-ci: Try harder to build all ARM targets Tom Rini
2016-11-07 1:17 ` Tom Rini [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=20161107011757.GO20830@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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