qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, f4bug@amsat.org,
	stefanha@redhat.com, crosa@redhat.com, pbonzini@redhat.com,
	"Alex Bennée" <alex.bennee@linaro.org>,
	aurelien@aurel32.net
Subject: [PATCH  v1 0/7] testing/next (hexagon 2, electric boogaloo)
Date: Wed, 10 Mar 2021 19:23:24 +0000	[thread overview]
Message-ID: <20210310192331.29284-1-alex.bennee@linaro.org> (raw)

Hi,

This is basically the bits I dropped out of the in-flight PR:

  pull-testing-docs-xen-updates-080321-2

In an attempt to avoid docker caching shenanigans I basically took the
fugly hammer to our existing over-engineered docker.py script to grow
new features to handle the case of images we don't want users to build
normally. I'm open to better approaches.

 - docker: Add Hexagon image
 - tests/docker: add "fetch" sub-command
 - tests/docker: allow "update" to add the current user
 - tests/docker: make executable an optional argument to "update"
 - tests/docker: fix copying of executable in "update"


Alessandro Di Federico (2):
  docker: Add Hexagon image
  tests/tcg: Use Hexagon Docker image

Alex Bennée (5):
  tests/docker: fix copying of executable in "update"
  tests/docker: make executable an optional argument to "update"
  tests/docker: allow "update" to add the current user
  tests/docker: add "fetch" sub-command
  gitlab: add build-user-hexagon test

 .gitlab-ci.yml                                |  11 ++
 MAINTAINERS                                   |   2 +
 tests/docker/Makefile.include                 |  24 ++-
 tests/docker/docker.py                        |  78 +++++++---
 .../dockerfiles/debian-hexagon-cross.docker   |  44 ++++++
 .../build-toolchain.sh                        | 141 ++++++++++++++++++
 tests/tcg/configure.sh                        |   4 +
 7 files changed, 282 insertions(+), 22 deletions(-)
 create mode 100644 tests/docker/dockerfiles/debian-hexagon-cross.docker
 create mode 100755 tests/docker/dockerfiles/debian-hexagon-cross.docker.d/build-toolchain.sh

-- 
2.20.1



             reply	other threads:[~2021-03-10 19:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 19:23 Alex Bennée [this message]
2021-03-10 19:23 ` [PATCH v1 1/7] tests/docker: fix copying of executable in "update" Alex Bennée
2021-03-10 19:23 ` [PATCH v1 2/7] tests/docker: make executable an optional argument to "update" Alex Bennée
2021-03-10 19:23 ` [PATCH v1 3/7] tests/docker: allow "update" to add the current user Alex Bennée
2021-03-10 19:23 ` [PATCH v1 4/7] tests/docker: add "fetch" sub-command Alex Bennée
2021-03-10 20:13   ` Philippe Mathieu-Daudé
2021-03-10 19:23 ` [PATCH v1 5/7] docker: Add Hexagon image Alex Bennée
2021-03-10 19:23 ` [PATCH v1 6/7] tests/tcg: Use Hexagon Docker image Alex Bennée
2021-03-10 19:23 ` [PATCH v1 7/7] gitlab: add build-user-hexagon test Alex Bennée
2021-03-10 19:45 ` [PATCH v1 0/7] testing/next (hexagon 2, electric boogaloo) no-reply

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=20210310192331.29284-1-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=berrange@redhat.com \
    --cc=crosa@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).