From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: "Lucas Mateus Castro(alqotel)" <lucas.araujo@eldorado.org.br>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH 0/8] Patch series to set up a ppc64le CI
Date: Tue, 6 Sep 2022 16:52:48 -0300 [thread overview]
Message-ID: <e8609bda-865f-42c8-9234-75b082ca9df0@gmail.com> (raw)
In-Reply-To: <20220727163632.59806-1-lucas.araujo@eldorado.org.br>
Lucas,
If you're still interested, patches 1-4 are worth re-sending in separate.
You'll need to address Daniel's comments on patch 1. The other 3 patches
LGTM.
Patches 5-8 can wait. We're not certain about Unicamp's Minicloud
availability in the future, so there's no point in setting up our CI
based on Minicloud's specifics.
Thanks,
Daniel
On 7/27/22 13:36, Lucas Mateus Castro(alqotel) wrote:
> This patch series aim to make easier to set up a compilation and CI
> environment in PPC64 and PPC64LE machines.
>
> The first 2 patches is a fix not related to ppc64.
> Patch 3 and 4 also affect some other architectures.
> Patches 5 to 7 are adding Power specific additions.
>
> Patch 8 is a RFC for a current way to run the docker tests in PPC64LE.
>
> Lucas Mateus Castro(alqotel) (8):
> tests/docker: Fix alpine dockerfile
> scripts/ci/setup: ninja missing from build-environment
> scripts/ci/setup: Fix libxen requirements
> scripts/ci/setup: spice-server only on x86 aarch64
> scripts/ci/setup: Add ppc64le to vars.yml template
> scripts/ci/setup: Add Fedora to build-environment.yml
> scripts/ci/setup: Added debian to build-environment.yml
> tests/docker: Selective line reading by python script
>
> scripts/ci/setup/build-environment.yml | 54 +++++++++++++++++++++-----
> scripts/ci/setup/vars.yml.template | 1 +
> tests/docker/docker.py | 15 +++++--
> tests/docker/dockerfiles/alpine.docker | 3 ++
> 4 files changed, 61 insertions(+), 12 deletions(-)
>
next prev parent reply other threads:[~2022-09-06 19:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 16:36 [PATCH 0/8] Patch series to set up a ppc64le CI Lucas Mateus Castro(alqotel)
2022-07-27 16:36 ` [PATCH 1/8] tests/docker: Fix alpine dockerfile Lucas Mateus Castro(alqotel)
2022-07-27 17:09 ` Daniel P. Berrangé
2022-07-27 17:23 ` Lucas Mateus Martins Araujo e Castro
2022-07-28 6:52 ` Thomas Huth
2022-07-28 7:06 ` Thomas Huth
2022-07-27 16:36 ` [PATCH 2/8] scripts/ci/setup: ninja missing from build-environment Lucas Mateus Castro(alqotel)
2022-07-27 16:36 ` [PATCH 3/8] scripts/ci/setup: Fix libxen requirements Lucas Mateus Castro(alqotel)
2022-09-07 17:24 ` Alex Bennée
2022-07-27 16:36 ` [PATCH 4/8] scripts/ci/setup: spice-server only on x86 aarch64 Lucas Mateus Castro(alqotel)
2022-07-27 16:36 ` [PATCH 5/8] scripts/ci/setup: Add ppc64le to vars.yml template Lucas Mateus Castro(alqotel)
2022-07-27 16:36 ` [PATCH 6/8] scripts/ci/setup: Add Fedora to build-environment.yml Lucas Mateus Castro(alqotel)
2022-07-27 16:36 ` [PATCH 7/8] scripts/ci/setup: Added debian " Lucas Mateus Castro(alqotel)
2022-07-27 16:36 ` [RFC PATCH 8/8] tests/docker: Selective line reading by python script Lucas Mateus Castro(alqotel)
2022-07-27 21:20 ` Philippe Mathieu-Daudé via
2022-07-28 8:43 ` Daniel P. Berrangé
2022-09-06 19:52 ` Daniel Henrique Barboza [this message]
2022-09-12 12:16 ` [PATCH 0/8] Patch series to set up a ppc64le CI Lucas Mateus Martins Araujo e Castro
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=e8609bda-865f-42c8-9234-75b082ca9df0@gmail.com \
--to=danielhb413@gmail.com \
--cc=lucas.araujo@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).