From: "Abner Chang" <abner.chang@hpe.com>
To: devel@edk2.groups.io
Cc: abner.chang@hpe.com, Bret Barkelew <Bret.Barkelew@microsoft.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Leif Lindholm <leif@nuviainc.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <liming.gao@intel.com>,
Gilbert Chen <gilbert.chen@hpe.com>,
Daniel Helmut Schaefer <daniel.schaefer@hpe.com>
Subject: [edk2-staging/RISC-V-V2: CI Config PATCH v1 0/6] RISC-V EDK2 CI configuration files.
Date: Sat, 29 Feb 2020 12:22:59 +0800 [thread overview]
Message-ID: <20200229042305.1794-1-abner.chang@hpe.com> (raw)
BZ:2562 - EDK CI for RISC-V architecture.
This set of patches enale RISC-V architecture on EDK2 CI test process.
Signed-off-by: Abner Chang <abner.chang@hpe.com>
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Leif Lindholm <leif@nuviainc.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Gilbert Chen <gilbert.chen@hpe.com>
Cc: Daniel Helmut Schaefer <daniel.schaefer@hpe.com>
Abner Chang (6):
RiscVPlatformPkg: Add RiscVPlatformPkg yaml file for EDK2 CI.
RiscVPkg: Add RiscVPkg yaml file for EDK2 CI.
MdeModulePkg: Revise MdeModulePkg yaml file for RISC-V EDK2 CI.
BaseTools: Enable RISC-V architecture for RISC-V EDK2 CI.
.azurepipelines: Add RISC-V architecture on RISC-V EDK2 CI.
.pytool: Add RISC-V architecture on RISC-V EDK2 CI.
.azurepipelines/Ubuntu-GCC5.yml | 3 +-
.pytool/CISettings.py | 15 +++-
.../Bin/gcc_riscv64_unknown_ext_dep.yaml | 21 +++++
.../LinuxGcc5ToolChain/LinuxGcc5ToolChain.py | 31 +++++++
MdeModulePkg/MdeModulePkg.ci.yaml | 3 +-
RiscVPkg/RiscVPkg.ci.yaml | 80 ++++++++++++++++++
RiscVPlatformPkg/RiscVPlatformPkg.ci.yaml | 81 +++++++++++++++++++
7 files changed, 229 insertions(+), 5 deletions(-)
create mode 100644 BaseTools/Bin/gcc_riscv64_unknown_ext_dep.yaml
create mode 100644 RiscVPkg/RiscVPkg.ci.yaml
create mode 100644 RiscVPlatformPkg/RiscVPlatformPkg.ci.yaml
--
2.25.0
next reply other threads:[~2020-02-29 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 4:22 Abner Chang [this message]
2020-02-29 4:23 ` [edk2-staging/RISC-V-V2: CI Config PATCH v1 1/6] RiscVPlatformPkg: Add RiscVPlatformPkg yaml file for EDK2 CI Abner Chang
2020-02-29 4:23 ` [edk2-staging/RISC-V-V2: CI Config PATCH v1 2/6] RiscVPkg: Add RiscVPkg " Abner Chang
2020-02-29 4:23 ` [edk2-staging/RISC-V-V2: CI Config PATCH v1 3/6] MdeModulePkg: Revise MdeModulePkg yaml file for RISC-V " Abner Chang
2020-02-29 4:23 ` [edk2-staging/RISC-V-V2: CI Config PATCH v1 4/6] BaseTools: Enable RISC-V architecture " Abner Chang
2020-02-29 4:23 ` [edk2-staging/RISC-V-V2: CI Config PATCH v1 5/6] .azurepipelines: Add RISC-V architecture on " Abner Chang
2020-02-29 4:23 ` [edk2-staging/RISC-V-V2: CI Config PATCH v1 6/6] .pytool: " Abner Chang
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-list 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=20200229042305.1794-1-abner.chang@hpe.com \
--to=devel@edk2.groups.io \
/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