From: "Abner Chang" <abner.chang@hpe.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"sean.brogan@microsoft.com" <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] [PATCH v1 0/3] Enable RISC-V architecture for RISC-V EDK2 CI.
Date: Sun, 26 Apr 2020 11:36:34 +0000 [thread overview]
Message-ID: <TU4PR8401MB04299DED8473E8D5B6082C17FFAE0@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <18612.1587785786895636119@groups.io>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
Here is the test PR based on the latest edk2 master with this patch set.
Thanks for reviewing this.
From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Sean via groups.io
Sent: Saturday, April 25, 2020 11:36 AM
To: Chang, Abner (HPS SW/FW Technologist) <abner.chang@hpe.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v1 0/3] Enable RISC-V architecture for RISC-V EDK2 CI.
Please run a a test PR with this patchset? I would like to see how it impacts the build times.
Patche series look fine to me.
Reviewed-by: Sean Brogan <sean.brogan@microsoft.com<mailto:sean.brogan@microsoft.com>>
[-- Attachment #2: Type: text/html, Size: 4064 bytes --]
prev parent reply other threads:[~2020-04-26 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 7:13 [PATCH v1 0/3] Enable RISC-V architecture for RISC-V EDK2 CI Abner Chang
2020-04-10 7:13 ` [PATCH v1 2/3] .azurepipelines: " Abner Chang
2020-04-10 7:13 ` [PATCH v1 3/3] .pytool: " Abner Chang
2020-04-25 3:36 ` [edk2-devel] [PATCH v1 0/3] " Sean
2020-04-26 11:36 ` Abner Chang [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-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=TU4PR8401MB04299DED8473E8D5B6082C17FFAE0@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.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