From: "Ni, Ray" <ray.ni@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] Patch List for 201908 stable tag
Date: Tue, 20 Aug 2019 18:47:25 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C28FF56@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4D3E44@SHSMSX104.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Liming,
Thanks for the confirmation. It has been pushed.
Thanks,
Ray
From: Gao, Liming
Sent: Monday, August 19, 2019 5:48 PM
To: Ni, Ray <ray.ni@intel.com>; devel@edk2.groups.io
Subject: RE: [edk2-devel] Patch List for 201908 stable tag
Ray:
It follows current soft feature freeze process. I am OK to fix it for this stable tag.
Thanks
Liming
From: Ni, Ray [mailto:ray.ni@intel.com]
Sent: Tuesday, August 20, 2019 2:05 AM
To: Gao; Gao, Liming <liming.gao@intel.com<mailto:liming.gao@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: Re: [edk2-devel] Patch List for 201908 stable tag
Liming, Below patch already got the reviewed-by tag before the freezing point. Can I push it now?
https://edk2.groups.io/g/devel/topic/32737146 UefiCpuPkg/PiSmmCpuDxeSmm: don't free page table pages that are required to handle current page fault
[-- Attachment #2: Type: text/html, Size: 5496 bytes --]
next prev parent reply other threads:[~2019-08-20 18:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A89E2EF3DFEDB4C8BFDE51014F606A14E4D25AD@SHSMSX104.ccr.corp.intel.com>
2019-08-16 8:00 ` Patch List for 201908 stable tag Liming Gao
2019-08-16 18:37 ` Laszlo Ersek
2019-08-19 23:28 ` Michael D Kinney
2019-08-17 1:06 ` Michael D Kinney
2019-08-19 18:04 ` [edk2-devel] " Ni, Ray
2019-08-20 0:48 ` Liming Gao
2019-08-20 18:47 ` Ni, Ray [this message]
2019-08-19 23:05 ` Ni, Ray
2019-08-19 23:29 ` Michael D Kinney
2019-08-20 17:02 ` Ni, Ray
2019-08-20 17:52 ` Andrew Fish
2019-08-20 18:47 ` Ni, Ray
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=734D49CCEBEEF84792F5B80ED585239D5C28FF56@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