From: "Abner Chang" <abner.chang@hpe.com>
To: devel@edk2.groups.io
Cc: abner.chang@hpe.com, Jiaxin Wu <jiaxin.wu@intel.com>,
Siyuan Fu <siyuan.fu@intel.com>,
Leif Lindholm <leif@nuviainc.com>,
Gilbert Chen <gilbert.chen@hpe.com>,
Daniel Helmut Schaefer <daniel.schaefer@hpe.com>
Subject: [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 3/9] NetworkPkg: Add RISC-V architecture for EDK2 CI.
Date: Sat, 29 Feb 2020 22:13:52 +0800 [thread overview]
Message-ID: <20200229141358.9528-4-abner.chang@hpe.com> (raw)
In-Reply-To: <20200229141358.9528-1-abner.chang@hpe.com>
BZ:2562
https://bugzilla.tianocore.org/show_bug.cgi?id=2562
EDK2 CI report:
https://github.com/tianocore/edk2-staging/pull/196
https://github.com/tianocore/edk2-staging/pull/197
Add RISC-V architecture for EDK2 CI testing.
Signed-off-by: Abner Chang <abner.chang@hpe.com>
Cc: Jiaxin Wu <jiaxin.wu@intel.com>
Cc: Siyuan Fu <siyuan.fu@intel.com>
Cc: Leif Lindholm <leif@nuviainc.com>
Cc: Gilbert Chen <gilbert.chen@hpe.com>
Cc: Daniel Helmut Schaefer <daniel.schaefer@hpe.com>
---
NetworkPkg/NetworkPkg.dsc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/NetworkPkg/NetworkPkg.dsc b/NetworkPkg/NetworkPkg.dsc
index b149453d26..503d828f91 100644
--- a/NetworkPkg/NetworkPkg.dsc
+++ b/NetworkPkg/NetworkPkg.dsc
@@ -3,7 +3,7 @@
#
# (C) Copyright 2014 Hewlett-Packard Development Company, L.P.<BR>
# Copyright (c) 2009 - 2018, Intel Corporation. All rights reserved.<BR>
-#
+# Copyright (c) 2020, Hewlett Packard Enterprise Development LP. All rights reserved.<BR>
# SPDX-License-Identifier: BSD-2-Clause-Patent
#
##
@@ -14,7 +14,7 @@
PLATFORM_VERSION = 0.98
DSC_SPECIFICATION = 0x00010005
OUTPUT_DIRECTORY = Build/NetworkPkg
- SUPPORTED_ARCHITECTURES = IA32|X64|EBC|ARM|AARCH64
+ SUPPORTED_ARCHITECTURES = IA32|X64|EBC|ARM|AARCH64|RISCV64
BUILD_TARGETS = DEBUG|RELEASE|NOOPT
SKUID_IDENTIFIER = DEFAULT
--
2.25.0
next prev parent reply other threads:[~2020-02-29 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 14:13 [edk2-staging/RISC-V-V2: RISC-V EDK2 CI PATCH v1 0/9] Necessary code changes for RISC-V EDK2 CI Abner Chang
2020-02-29 14:13 ` [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 1/9] FatPkg: Add RISC-V architecture for " Abner Chang
2020-02-29 14:13 ` [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 2/9] FmpDevicePkg: " Abner Chang
2020-02-29 14:13 ` Abner Chang [this message]
2020-02-29 14:13 ` [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 4/9] NetworkPkg/HttpBootDxe: " Abner Chang
2020-02-29 14:13 ` [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 5/9] CryptoPkg: " Abner Chang
2020-02-29 14:13 ` [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 6/9] MdePkg/Include: Add RISC-V related definitions " Abner Chang
2020-02-29 14:13 ` [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 7/9] SecurityPkg: Security package changes for RISC-V " Abner Chang
2020-03-01 0:23 ` [edk2-devel] " Yao, Jiewen
2020-02-29 14:13 ` [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 8/9] ShellPkg: Shell " Abner Chang
2020-02-29 14:13 ` [edk2-staging/RISC-V-V2: RISC-V EDK2 CI Code Change PATCH v1 9/9] UnitTestFrameworkPkg: Add RISC-V architecture " Abner Chang
2020-03-04 10:22 ` [edk2-devel] [edk2-staging/RISC-V-V2: RISC-V EDK2 CI PATCH v1 0/9] Necessary code changes " Maciej Rabeda
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=20200229141358.9528-4-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