From: "Liming Gao" <liming.gao@intel.com>
To: Robert Phelps <Robert@ami.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Oleksiy Yakovlev <Oleksiyy@ami.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Felix Polyudov <Felixp@ami.com>
Subject: Re: [edk2-devel] [PATCH v2 0/5] Add Definitions introduced in PI 1.7 and PI 1.7a
Date: Thu, 14 May 2020 16:39:03 +0000 [thread overview]
Message-ID: <BN6PR11MB397219171FB9805EB9863FCE80BC0@BN6PR11MB3972.namprd11.prod.outlook.com> (raw)
In-Reply-To: <021F612F2D7DCB42BAF99452B742A2ED0440193846@atlms1.us.megatrends.com>
You don't need do more. I will help merge this patch set.
> -----Original Message-----
> From: Robert Phelps <Robert@ami.com>
> Sent: Friday, May 15, 2020 12:36 AM
> To: Gao, Liming <liming.gao@intel.com>; devel@edk2.groups.io; Oleksiy Yakovlev <Oleksiyy@ami.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Felix Polyudov <Felixp@ami.com>
> Subject: RE: [edk2-devel] [PATCH v2 0/5] Add Definitions introduced in PI 1.7 and PI 1.7a
>
> I apologize, but I am new to this. At this point, I have done the patches and the Patch updates and I have created the Pull Request.
> What is my next step, or is that all I need to do?
>
> Rob Phelps
>
> -----Original Message-----
> From: Gao, Liming <liming.gao@intel.com>
> Sent: Wednesday, May 13, 2020 12:35 PM
> To: devel@edk2.groups.io; Oleksiy Yakovlev <Oleksiyy@ami.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Felix Polyudov <Felixp@ami.com>; Robert Phelps <Robert@ami.com>
> Subject: RE: [edk2-devel] [PATCH v2 0/5] Add Definitions introduced in PI 1.7 and PI 1.7a
>
> Reviewed-by: Liming Gao <liming.gao@intel.com> for the full patch set.
>
> Besides, 3/5 patch has been merged into edk2 by Ard patch set.
>
> Thanks
> Liming
> > -----Original Message-----
> > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Oleksiy
> > Yakovlev
> > Sent: Tuesday, May 12, 2020 4:24 AM
> > To: devel@edk2.groups.io
> > Cc: Gao, Liming <liming.gao@intel.com>; Kinney, Michael D
> > <michael.d.kinney@intel.com>; Felixp@ami.com; oleksiyy@ami.com;
> > robert@ami.com
> > Subject: [edk2-devel] [PATCH v2 0/5] Add Definitions introduced in PI
> > 1.7 and PI 1.7a
> >
> > From: Robert Phelps <robert@ami.com>
> >
> > The following patches add and update the current structures and
> > definitions that were introduced by the PI 1.7 and PI 1.7a
> > specifications
> >
> > Signed-off-by: Robert Phelps <robert@ami.com>
> >
> > Robert Phelps (5):
> > MdePkg: New Status Codes
> > MdePkg: Updates to PI 1.7 Revision numbers for PEI and DXE
> > MdePkg: EFI_MM_COMUNICATION2_PROTOCOL
> > MdePkg: Added header file for Delayed Dispatch PPI
> > MdePkg: Updates to structures in the MP Services Protocol
> >
> > MdePkg/Include/Pi/PiDxeCis.h | 4 +-
> > MdePkg/Include/Pi/PiPeiCis.h | 4 +-
> > MdePkg/Include/Pi/PiStatusCode.h | 17 ++++-
> > MdePkg/Include/Ppi/DelayedDispatch.h | 85 ++++++++++++++++++++++
> > MdePkg/Include/Protocol/MmCommunication2.h | 72 ++++++++++++++++++
> > MdePkg/Include/Protocol/MpService.h | 50 +++++++++++++
> > MdePkg/MdePkg.dec | 10 +++
> > 7 files changed, 236 insertions(+), 6 deletions(-) create mode
> > 100644 MdePkg/Include/Ppi/DelayedDispatch.h
> > create mode 100644 MdePkg/Include/Protocol/MmCommunication2.h
> >
> > --
> > 2.24.1.windows.2
> >
> >
> > Please consider the environment before printing this email.
> >
> > The information contained in this message may be confidential and
> > proprietary to American Megatrends (AMI). This communication is
> > intended to be read only by the individual or entity to whom it is
> > addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution
> of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600,
> and then delete or destroy all copies of the transmission.
> >
> >
>
>
> Please consider the environment before printing this email.
>
> The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication
> is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is
> not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please
> promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
next prev parent reply other threads:[~2020-05-14 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 20:24 [PATCH v2 0/5] Add Definitions introduced in PI 1.7 and PI 1.7a Oleksiy Yakovlev
2020-05-11 20:24 ` [PATCH v2 1/5] MdePkg: New Status Codes Oleksiy Yakovlev
2020-05-11 20:24 ` [PATCH v2 2/5] MdePkg: Updates to PI 1.7 Revision numbers for Oleksiy Yakovlev
2020-05-11 20:24 ` [PATCH v2 3/5] MdePkg: EFI_MM_COMUNICATION2_PROTOCOL Oleksiy Yakovlev
2020-05-11 20:24 ` [PATCH v2 4/5] MdePkg: Added header file for Delayed Dispatch PPI Oleksiy Yakovlev
2020-05-11 20:24 ` [PATCH v2 5/5] MdePkg: Update structures for MpServices Protocol Oleksiy Yakovlev
2020-05-13 16:35 ` [edk2-devel] [PATCH v2 0/5] Add Definitions introduced in PI 1.7 and PI 1.7a Liming Gao
2020-05-14 16:35 ` robert
2020-05-14 16:39 ` Liming Gao [this message]
2020-05-14 16:51 ` Robert Phelps
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=BN6PR11MB397219171FB9805EB9863FCE80BC0@BN6PR11MB3972.namprd11.prod.outlook.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