From: Jamin Lin via <qemu-arm@nongnu.org>
To: "Cédric Le Goater" <clg@kaod.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Troy Lee" <leetroy@gmail.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Joel Stanley" <joel@jms.id.au>,
"open list:ASPEED BMCs" <qemu-arm@nongnu.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Cc: <jamin_lin@aspeedtech.com>, <troy_lee@aspeedtech.com>
Subject: [PATCH v1 0/3] Update to test new ASPEED SDK version
Date: Tue, 22 Apr 2025 17:15:00 +0800 [thread overview]
Message-ID: <20250422091504.3666464-1-jamin_lin@aspeedtech.com> (raw)
v1:
Update to test new ASPEED SDK version for AST2600, AST2500 ,and AST1030.
Jamin Lin (3):
tests/functional/aspeed: Update test ASPEED SDK v09.06 for AST2500
tests/functional/aspeed: Update test ASPEED SDK v09.06 for AST2500
tests/functional/aspeed: Update test ASPEED SDK v03.00 for AST1030
tests/functional/test_arm_aspeed_ast1030.py | 40 ++++-----------------
tests/functional/test_arm_aspeed_ast2500.py | 8 ++---
tests/functional/test_arm_aspeed_ast2600.py | 15 ++++----
3 files changed, 19 insertions(+), 44 deletions(-)
--
2.43.0
WARNING: multiple messages have this Message-ID (diff)
From: Jamin Lin via <qemu-devel@nongnu.org>
To: "Cédric Le Goater" <clg@kaod.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Troy Lee" <leetroy@gmail.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Joel Stanley" <joel@jms.id.au>,
"open list:ASPEED BMCs" <qemu-arm@nongnu.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Cc: <jamin_lin@aspeedtech.com>, <troy_lee@aspeedtech.com>
Subject: [PATCH v1 0/3] Update to test new ASPEED SDK version
Date: Tue, 22 Apr 2025 17:15:00 +0800 [thread overview]
Message-ID: <20250422091504.3666464-1-jamin_lin@aspeedtech.com> (raw)
v1:
Update to test new ASPEED SDK version for AST2600, AST2500 ,and AST1030.
Jamin Lin (3):
tests/functional/aspeed: Update test ASPEED SDK v09.06 for AST2500
tests/functional/aspeed: Update test ASPEED SDK v09.06 for AST2500
tests/functional/aspeed: Update test ASPEED SDK v03.00 for AST1030
tests/functional/test_arm_aspeed_ast1030.py | 40 ++++-----------------
tests/functional/test_arm_aspeed_ast2500.py | 8 ++---
tests/functional/test_arm_aspeed_ast2600.py | 15 ++++----
3 files changed, 19 insertions(+), 44 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-22 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 9:15 Jamin Lin via [this message]
2025-04-22 9:15 ` [PATCH v1 0/3] Update to test new ASPEED SDK version Jamin Lin via
2025-04-22 9:15 ` [PATCH v1 1/3] tests/functional/aspeed: Update test ASPEED SDK v09.06 for AST2500 Jamin Lin via
2025-04-22 11:58 ` Cédric Le Goater
2025-04-22 9:15 ` [PATCH v1 2/3] " Jamin Lin via
2025-04-22 9:15 ` Jamin Lin via
2025-04-22 12:00 ` Cédric Le Goater
2025-04-22 9:15 ` [PATCH v1 3/3] tests/functional/aspeed: Update test ASPEED SDK v03.00 for AST1030 Jamin Lin via
2025-04-22 9:15 ` Jamin Lin via
2025-04-22 11:41 ` Philippe Mathieu-Daudé
2025-04-22 11:58 ` Cédric Le Goater
2025-04-23 1:23 ` Jamin Lin
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=20250422091504.3666464-1-jamin_lin@aspeedtech.com \
--to=qemu-arm@nongnu.org \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=leetroy@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=steven_lee@aspeedtech.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.