From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <sivaparvathic@ami.com>
Subject: 回复: [edk2-devel] 回复: [edk2-devel] [PATCH] [PATCH]MdeModulePkg/Ufs: Coverity scan flags multiple issues in edk2-stable202205 Signed-off-by: sivaparvathic@ami.com
Date: Sat, 8 Oct 2022 09:53:59 +0800 [thread overview]
Message-ID: <000701d8dab8$d59ddd00$80d99700$@byosoft.com.cn> (raw)
In-Reply-To: <3572.1665044238551294558@groups.io>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
I have gave my reviewed-by https://edk2.groups.io/g/devel/message/93694.
But, I can’t get this patch from the mail. Can you share this patch in Pull Request or your fork GitHub Edk2 repo branch?
Thanks
Liming
发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 sivaparvathi C via groups.io
发送时间: 2022年10月6日 16:17
收件人: gaoliming <gaoliming@byosoft.com.cn>; devel@edk2.groups.io
主题: Re: [edk2-devel] 回复: [edk2-devel] [PATCH] [PATCH]MdeModulePkg/Ufs: Coverity scan flags multiple issues in edk2-stable202205 Signed-off-by: sivaparvathic@ami.com
On Tue, Sep 13, 2022 at 10:44 AM, gaoliming wrote:
gaoliming
Hi GaoLiming,
Could you please review the changes?
Thanks,
Sivaparvathi
[-- Attachment #2: Type: text/html, Size: 4542 bytes --]
next prev parent reply other threads:[~2022-10-08 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 4:01 [PATCH] [PATCH]MdeModulePkg/Ufs: Coverity scan flags multiple issues in edk2-stable202205 Signed-off-by: sivaparvathic@ami.com sivaparvathi C
2022-09-12 9:08 ` [edk2-devel] " sivaparvathi C
2022-09-13 5:14 ` 回复: " gaoliming
2022-10-06 8:17 ` [edk2-devel] " sivaparvathi C
2022-10-08 1:53 ` gaoliming [this message]
2022-10-13 11:18 ` [edk2-devel] 回复: " sivaparvathi C
2022-10-17 5:17 ` 回复: " gaoliming
2022-10-28 8:04 ` [edk2-devel] " sivaparvathi C
2022-11-01 1:52 ` 回复: " gaoliming
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='000701d8dab8$d59ddd00$80d99700$@byosoft.com.cn' \
--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