From: Joel Stanley <joel@jms.id.au>
To: "Cédric Le Goater" <clg@kaod.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Cc: Andrew Jeffery <andrew@aj.id.au>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: [PATCH 0/2] tests/acceptance: Test Aspeed ARM machines
Date: Wed, 3 Mar 2021 11:52:15 +1030 [thread overview]
Message-ID: <20210303012217.637737-1-joel@jms.id.au> (raw)
This adds tests for the Aspeed ARM SoCs. The AST2400 and AST2500 tests
use OpenBMC images from that project, fetched from github releases. The
AST2600 test uses a Debian arm32 kernel.
Note that the ast2600 test will fail if [1] is not applied. I have
tested locally and all seems good.
I note that checkpatch warns about a couple of lines over 80 columns in
this file. Can we agree to relax this restriction for this file, as it
helps the readability of the constants such as sha hashes and URLs?
[1] https://lore.kernel.org/qemu-devel/20210303010505.635621-1-joel@jms.id.au/T/#u
Joel Stanley (2):
tests/acceptance: Test ast2400 and ast2500 machines
tests/acceptance: Test ast2600 machine
tests/acceptance/boot_linux_console.py | 72 ++++++++++++++++++++++++++
1 file changed, 72 insertions(+)
--
2.30.1
next reply other threads:[~2021-03-03 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 1:22 Joel Stanley [this message]
2021-03-03 1:22 ` [PATCH 1/2] tests/acceptance: Test ast2400 and ast2500 machines Joel Stanley
2021-03-03 7:44 ` Cédric Le Goater
2021-03-03 10:19 ` Philippe Mathieu-Daudé
2021-03-03 11:19 ` Joel Stanley
2021-03-04 13:29 ` Philippe Mathieu-Daudé
2021-03-03 1:22 ` [PATCH 2/2] tests/acceptance: Test ast2600 machine Joel Stanley
2021-03-03 7:43 ` Cédric Le Goater
2021-03-03 9:32 ` Joel Stanley
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=20210303012217.637737-1-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=crosa@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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).