From: "Kun Qin" <kuqin12@gmail.com>
To: devel@edk2.groups.io, vincent.zimmer@intel.com, "Gao,
Liming" <gaoliming@byosoft.com.cn>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "afish@apple.com" <afish@apple.com>,
"leif@nuviainc.com" <leif@nuviainc.com>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: 回复: [edk2-devel] Request for PI spec change
Date: Tue, 15 Mar 2022 14:41:28 -0700 [thread overview]
Message-ID: <5fe2e036-9fc9-1ed6-bb15-eb5cd1b81748@gmail.com> (raw)
In-Reply-To: <BN6PR11MB005134B0599E43A9E2B08D6288109@BN6PR11MB0051.namprd11.prod.outlook.com>
Thank you for the help, Vincent!
Could you please let me know if there is anything I need to do in the
meantime?
Regards,
Kun
On 3/15/2022 2:39 PM, Zimmer, Vincent wrote:
> Sounds like we need to open a UEFI Forum Mantis under the PIWG in order to propagate this clean-up into the next PI specification based upon https://github.com/tianocore/edk2-staging/tree/BZ3794-expand_status_codes. I can take care of that next step along w/ queuing up other topics for an upcoming PIWG meeting.
>
> Vincent
>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Kun Qin
> Sent: Tuesday, March 15, 2022 10:30 AM
> To: devel@edk2.groups.io; Gao, Liming <gaoliming@byosoft.com.cn>; Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: afish@apple.com; leif@nuviainc.com; Liu, Zhiguang <zhiguang.liu@intel.com>
> Subject: Re: 回复: [edk2-devel] Request for PI spec change
>
> 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_c
>>> od
>>> 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
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>
prev parent reply other threads:[~2022-03-15 21:41 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
2022-03-15 21:39 ` Zimmer, Vincent
2022-03-15 21:41 ` Kun Qin [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=5fe2e036-9fc9-1ed6-bb15-eb5cd1b81748@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