From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] travis: Split and rename xilinx ARM in to two jobs
Date: Tue, 15 Oct 2019 08:42:11 -0400 [thread overview]
Message-ID: <20191015124211.GL16029@bill-the-cat> (raw)
In-Reply-To: <9fcd747f-aa36-e394-c513-997c6fa15370@xilinx.com>
On Tue, Oct 15, 2019 at 02:14:54PM +0200, Michal Simek wrote:
> On 15. 10. 19 13:27, Tom Rini wrote:
> > Split the ARMv7 and AArch64 platforms into separate jobs, to avoid them
> > taking too long to build overall. Also rename them from "Xilinx" to
> > "Zynq*" to reflect slightly better what is being built and to pull in a
> > few more board matches.
> >
> > Cc: Michal Simek <michal.simek@xilinx.com>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > .travis.yml | 11 +++++++----
> > 1 file changed, 7 insertions(+), 4 deletions(-)
> >
> > diff --git a/.travis.yml b/.travis.yml
> > index ced44deb1b69..d54f8b3b1e36 100644
> > --- a/.travis.yml
> > +++ b/.travis.yml
> > @@ -248,7 +248,7 @@ matrix:
> > - BUILDMAN="sun50i"
> > - name: "buildman catch-all ARM"
> > env:
> > - - BUILDMAN="arm -x arm11,arm7,arm9,aarch64,at91,bcm,freescale,kirkwood,mvebu,siemens,tegra,uniphier,mx,samsung,sunxi,am33xx,omap,pxa,rockchip,toradex,socfpga,k2,k3,xilinx"
> > + - BUILDMAN="arm -x arm11,arm7,arm9,aarch64,at91,bcm,freescale,kirkwood,mvebu,siemens,tegra,uniphier,mx,samsung,sunxi,am33xx,omap,pxa,rockchip,toradex,socfpga,k2,k3,zynq"
> > - name: "buildman sandbox x86"
> > env:
> > - BUILDMAN="sandbox x86"
> > @@ -322,7 +322,7 @@ matrix:
> > - BUILDMAN="uniphier"
> > - name: "buildman catch-all AArch64"
> > env:
> > - - BUILDMAN="aarch64 -x bcm,k3,tegra,ls1,ls2,mvebu,uniphier,sunxi,samsung,rockchip,xilinx"
> > + - BUILDMAN="aarch64 -x bcm,k3,tegra,ls1,ls2,mvebu,uniphier,sunxi,samsung,rockchip,zynq"
> > - name: "buildman rockchip"
> > env:
> > - BUILDMAN="rockchip"
> > @@ -330,9 +330,12 @@ matrix:
> > env:
> > - BUILDMAN="sh -x arm"
> > TOOLCHAIN="sh"
> > - - name: "buildman Xilinx (ARM)"
> > + - name: "buildman Zynq* (ARMv7)"
> > env:
> > - - BUILDMAN="xilinx -x microblaze"
> > + - BUILDMAN="zynq&armv7"
> > + - name: "buildman Zynq* (AArch64)"
> > + env:
> > + - BUILDMAN="zynq&aarch64"
>
> This is not exactly what was written above because it versal is missing.
> It means here should be zynq at aarch64 or better zynqmp at aarch64 versal at aarch64
OK, thanks, v2 coming up. Note that versal would have been covered in
the aarch64 catch-all job in v1.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191015/62fcb6a1/attachment.sig>
next prev parent reply other threads:[~2019-10-15 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 11:27 [U-Boot] [PATCH 1/3] travis: Split i.MX jobs a bit more Tom Rini
2019-10-15 11:27 ` [U-Boot] [PATCH 2/3] travis: Split sun8i in to two jobs Tom Rini
2019-10-17 11:25 ` Tom Rini
2019-10-15 11:27 ` [U-Boot] [PATCH 3/3] travis: Split and rename xilinx ARM " Tom Rini
2019-10-15 12:14 ` Michal Simek
2019-10-15 12:42 ` Tom Rini [this message]
2019-10-15 12:43 ` [U-Boot] [PATCHv2 " Tom Rini
2019-10-15 13:53 ` [U-Boot] [PATCHv3 " Tom Rini
2019-10-15 14:23 ` Michal Simek
2019-10-17 11:25 ` Tom Rini
2019-10-15 11:31 ` [U-Boot] [PATCH 1/3] travis: Split i.MX jobs a bit more Stefano Babic
2019-10-17 11:25 ` Tom Rini
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=20191015124211.GL16029@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