From: "Sunil V L" <sunilvl@ventanamicro.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn
Subject: Re: 回复: [edk2-devel] 回复: [edk2-stable202302 PATCH V2 1/1] OvmfPkg/RiscVVirt: Add Stack HOB
Date: Thu, 2 Mar 2023 12:20:26 +0530 [thread overview]
Message-ID: <01c5e527-a073-1c07-1053-9db39c83589d@ventanamicro.com> (raw)
In-Reply-To: <00e501d94c4c$c08753a0$4195fae0$@byosoft.com.cn>
Thank yo very much!, Liming.
On 01/03/23 20:17, gaoliming via groups.io wrote:
> Sunil:
> PR https://github.com/tianocore/edk2/pull/4084 has been created for this
> patch.
>
> Thanks
> Liming
>> -----邮件原件-----
>> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Sunil V L
>> 发送时间: 2023年2月28日 14:47
>> 收件人: devel@edk2.groups.io; gaoliming@byosoft.com.cn
>> 抄送: 'Andrei Warkentin' <andrei.warkentin@intel.com>; 'Ard Biesheuvel'
>> <ardb+tianocore@kernel.org>; 'Jiewen Yao' <jiewen.yao@intel.com>; 'Jordan
>> Justen' <jordan.l.justen@intel.com>; 'Gerd Hoffmann' <kraxel@redhat.com>;
>> 'Michael D Kinney' <michael.d.kinney@intel.com>; 'Andrew Fish'
>> <afish@apple.com>; 'Leif Lindholm' <leif@nuviainc.com>
>> 主题: Re: [edk2-devel] 回复: [edk2-stable202302 PATCH V2 1/1]
>> OvmfPkg/RiscVVirt: Add Stack HOB
>>
>> On Tue, Feb 28, 2023 at 02:43:13PM +0800, gaoliming via groups.io wrote:
>>> Sunil:
>>> Is this a critical issue? Dose this fix need to catch this stable tag?
> Has
>>> it been verified and code review?
>>>
>> Hi Liming,
>>
>> Yes, this is a critical issue. So, I request to catch the stable tag.
>>
>> Andrei who reported this issue has verified the fix and helped with
>> review.
>>
>> https://edk2.groups.io/g/devel/message/100496
>>
>> Thanks!
>> Sunil
>>
>>
>>
>>
>
>
>
>
>
>
>
prev parent reply other threads:[~2023-03-02 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 5:32 [edk2-stable202302 PATCH V2 1/1] OvmfPkg/RiscVVirt: Add Stack HOB Sunil V L
2023-02-28 6:43 ` 回复: " gaoliming
2023-02-28 6:47 ` [edk2-devel] " Sunil V L
2023-03-01 14:47 ` 回复: " gaoliming
2023-03-02 6:50 ` Sunil V L [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=01c5e527-a073-1c07-1053-9db39c83589d@ventanamicro.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