From: "gaoliming" <gaoliming@byosoft.com.cn>
To: "'Chuang, Marlboro'" <Marlboro.Chuang@dell.com>, <devel@edk2.groups.io>
Subject: 回复: [Bug 3187] FaultTolerantWriteDxe defect will cause NVRAM not recovered after number of WorkSpaceRefresh().
Date: Thu, 4 Feb 2021 14:55:08 +0800 [thread overview]
Message-ID: <006101d6fac2$aceb27a0$06c176e0$@byosoft.com.cn> (raw)
In-Reply-To: <MWHPR19MB1231C17D55B32E177B0537B4FFB49@MWHPR19MB1231.namprd19.prod.outlook.com>
Chuang:
I see you directly use IO port 0x70, 0x71. What purpose to use them?
Thanks
Liming
> -----邮件原件-----
> 发件人: Chuang, Marlboro <Marlboro.Chuang@dell.com>
> 发送时间: 2021年2月3日 12:59
> 收件人: devel@edk2.groups.io
> 抄送: gaoliming@byosoft.com.cn
> 主题: RE: [Bug 3187] FaultTolerantWriteDxe defect will cause NVRAM not
> recovered after number of WorkSpaceRefresh().
>
> Hi All,
>
> Regarding to Bug 3187, I have the duplicated code change and fix code change
> as the attachment.
> Please help to review and refine it.
>
> Thanks and Regards,
> Marlboro.
>
>
> -----Original Message-----
> From: bugzilla-daemon@bugzilla.tianocore.org
> <bugzilla-daemon@bugzilla.tianocore.org>
> Sent: Wednesday, February 3, 2021 11:04 AM
> To: Chuang, Marlboro
> Subject: [Bug 3187] FaultTolerantWriteDxe defect will cause NVRAM not
> recovered after number of WorkSpaceRefresh().
>
>
> [EXTERNAL EMAIL]
>
> https://bugzilla.tianocore.org/show_bug.cgi?id=3187
>
> gaoliming@byosoft.com.cn changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Priority|Lowest |Normal
> Status|UNCONFIRMED |CONFIRMED
> CC|
> |gaoliming@byosoft.com.cn
> Assignee|unassigned@tianocore.org
> |Marlboro.Chuang@dell.com
> Ever confirmed|0 |1
>
> --- Comment #2 from gaoliming@byosoft.com.cn ---
> @Marlboro: can you send your patch to edk2 mail list?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You are the assignee for the bug.
> You reported the bug.
next prev parent reply other threads:[~2021-02-04 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-3187-864@https.bugzilla.tianocore.org/>
[not found] ` <bug-3187-864-FpW5Oe9qGp@https.bugzilla.tianocore.org/>
2021-02-03 4:58 ` [Bug 3187] FaultTolerantWriteDxe defect will cause NVRAM not recovered after number of WorkSpaceRefresh() Chuang, Marlboro
2021-02-04 6:55 ` gaoliming [this message]
2021-02-04 7:08 ` marlboro.chuang
2021-02-05 3:03 ` [edk2-devel] " Keysound Chang
[not found] ` <1660BAEDAFD15740.32361@groups.io>
2021-02-05 11:11 ` Keysound Chang
2021-02-06 5:54 ` Chuang, Marlboro
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='006101d6fac2$aceb27a0$06c176e0$@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