From: "Kun Qin" <kuqin12@gmail.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn,
michael.d.kinney@intel.com
Cc: afish@apple.com, leif@nuviainc.com, zhiguang.liu@intel.com
Subject: Re: 回复: [edk2-devel] Request for PI spec change
Date: Tue, 15 Mar 2022 10:29:47 -0700 [thread overview]
Message-ID: <321eb5bc-c63c-7e36-785d-e549f81af85a@gmail.com> (raw)
In-Reply-To: <040e01d82dd8$20bad290$623077b0$@byosoft.com.cn>
Thanks for the review, Liming.
Could you please also shed some light on what the next steps are?
Thanks,
Kun
On 3/1/2022 5:52 PM, gaoliming wrote:
> Kun:
> The change looks good to me. Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
>
> Thanks
> Liming
>> -----邮件原件-----
>> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Kun Qin
>> 发送时间: 2022年3月2日 3:33
>> 收件人: devel@edk2.groups.io; michael.d.kinney@intel.com
>> 抄送: afish@apple.com; leif@nuviainc.com; gaoliming@byosoft.com.cn;
>> zhiguang.liu@intel.com
>> 主题: [edk2-devel] Request for PI spec change
>>
>> Hi edk2 maintainers,
>>
>> I have been trying to propose a PI spec change to extend status code
>> definitions.
>>
>> The proposed PI spec change along with the code change around this proposal
>> are all pushed to edk2-staging repo:
>> https://github.com/tianocore/edk2-staging/tree/BZ3794-expand_status_cod
>> es
>>
>> Could you please help reviewing the change and provide feedback? If there is
>> anything I missed in the code-process, please let me know as well.
>>
>> Thanks,
>> Kun
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2022-03-15 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 19:33 Request for PI spec change Kun Qin
2022-03-02 1:52 ` 回复: [edk2-devel] " gaoliming
2022-03-15 17:29 ` Kun Qin [this message]
2022-03-15 21:39 ` Zimmer, Vincent
2022-03-15 21:41 ` Kun Qin
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=321eb5bc-c63c-7e36-785d-e549f81af85a@gmail.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