From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Chen, Kenji" <kenji.chen@intel.com>
Subject: Re: Patch for Bug 2236 on Bugzilla
Date: Wed, 9 Oct 2019 13:37:31 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E514DF8@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <A7A4B3ECFA40144E98B82E71E29693557F59271E@PGSMSX108.gar.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
Kenji:
Please use git format-patch -1 to generate the patch, then use git send-email xxx.patch to send this patch to devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Besides, is there the track in edk2 https://bugzilla.tianocore.org/? If no, can you submit one?
Thanks
Liming
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Chen, Kenji
Sent: Wednesday, October 9, 2019 4:00 PM
To: devel@edk2.groups.io
Subject: [edk2-devel] Patch for Bug 2236 on Bugzilla
Commit Message:
FmpDevicePkg: Deferred LSV Commit after Platform Health Check
- LSV variable in each FmpDevice is updated after each successful FmpSetImage invocation. This blocks the deferred SVN mechanism performed by platfor side. Add a PCD to remove it to make platform code feasible to handle the mechanism of deferred LSV commit.
- Add FmpDevieSetImageEx function to delivr LsvUpdate parameter for FmpDeviceSetImage function. The value is from Fmp capsule image header to indicate platform side this is a LSV update.
[-- Attachment #2: Type: text/html, Size: 5418 bytes --]
next prev parent reply other threads:[~2019-10-09 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 7:59 Patch for Bug 2236 on Bugzilla Chen, Kenji
2019-10-09 13:37 ` Liming Gao [this message]
2019-10-09 16:12 ` Chen, Kenji
2019-10-09 16:44 ` Chen, Kenji
2019-10-10 6:28 ` [edk2-devel] " Sean
2019-10-14 3:52 ` Chen, Kenji
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E514DF8@SHSMSX104.ccr.corp.intel.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