All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: "Cédric Le Goater" <clg@redhat.com>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: Joel Stanley <joel@jms.id.au>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	Troy Lee <troy_lee@aspeedtech.com>,
	Jamin Lin <jamin_lin@aspeedtech.com>,
	Steven Lee <steven_lee@aspeedtech.com>,
	Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 0/5] tests/functional: Update Aspeed OpenBMC images (resend)
Date: Wed, 5 Feb 2025 08:31:17 +0100	[thread overview]
Message-ID: <8b33436d-6fda-4fc8-b9ae-9eb32b284337@kaod.org> (raw)
In-Reply-To: <20250129071820.1258133-1-clg@redhat.com>

On 1/29/25 08:18, Cédric Le Goater wrote:
> Hello,
> 
> This series updates the OpenBMC firmware images to the latest version
> for existing tests and also adds 2 new tests for Aspeed machines which
> were not tested before : witherspoon and bletchley.
> 
> Thanks,
> 
> C.
> 
> Cédric Le Goater (5):
>    tests/functional: Introduce a new test routine for OpenBMC images
>    tests/functional: Update OpenBMC image of palmetto machine
>    tests/functional: Update OpenBMC image of romulus machine
>    tests/functional: Introduce a witherspoon machine test
>    tests/functional: Introduce a bletchley machine test
> 
>   tests/functional/aspeed.py                    | 20 +++++++++-------
>   tests/functional/meson.build                  |  4 ++++
>   tests/functional/test_arm_aspeed_bletchley.py | 24 +++++++++++++++++++
>   tests/functional/test_arm_aspeed_palmetto.py  | 12 +++++-----
>   tests/functional/test_arm_aspeed_romulus.py   | 12 +++++-----
>   .../functional/test_arm_aspeed_witherspoon.py | 24 +++++++++++++++++++
>   6 files changed, 75 insertions(+), 21 deletions(-)
>   create mode 100755 tests/functional/test_arm_aspeed_bletchley.py
>   create mode 100755 tests/functional/test_arm_aspeed_witherspoon.py
> 


Applied to aspeed-next.

Thanks,

C.



      parent reply	other threads:[~2025-02-05  7:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29  7:18 [PATCH 0/5] tests/functional: Update Aspeed OpenBMC images (resend) Cédric Le Goater
2025-01-29  7:18 ` [PATCH 1/5] tests/functional: Introduce a new test routine for OpenBMC images Cédric Le Goater
2025-01-29  7:58   ` Thomas Huth
2025-01-29 16:28     ` Cédric Le Goater
2025-01-30  6:40       ` Thomas Huth
2025-01-30  8:01         ` Cédric Le Goater
2025-01-29  7:18 ` [PATCH 2/5] tests/functional: Update OpenBMC image of palmetto machine Cédric Le Goater
2025-01-29  8:00   ` Thomas Huth
2025-01-29  7:18 ` [PATCH 3/5] tests/functional: Update OpenBMC image of romulus machine Cédric Le Goater
2025-01-29  8:01   ` Thomas Huth
2025-01-29  7:18 ` [PATCH 4/5] tests/functional: Introduce a witherspoon machine test Cédric Le Goater
2025-01-29  9:02   ` Thomas Huth
2025-01-29  7:18 ` [PATCH 5/5] tests/functional: Introduce a bletchley " Cédric Le Goater
2025-01-30  7:54   ` Thomas Huth
2025-01-31 11:22   ` Patrick Williams
2025-01-31 12:28     ` Cédric Le Goater
2025-02-05  7:31 ` Cédric Le Goater [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=8b33436d-6fda-4fc8-b9ae-9eb32b284337@kaod.org \
    --to=clg@kaod.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=clg@redhat.com \
    --cc=jamin_lin@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=steven_lee@aspeedtech.com \
    --cc=thuth@redhat.com \
    --cc=troy_lee@aspeedtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.