public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Thomas Abraham <thomas.abraham@arm.com>,
	Sughosh Ganu <sng.lists@gmail.com>
Cc: Supreeth Venkatesh <supreeth.venkatesh@arm.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH v3 00/17] *** Standalone Management Mode Core Interface for AARCH64 Platforms ***
Date: Mon, 18 Jun 2018 15:12:46 +0000	[thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503AC4EE35@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CAJuA9ai6H8CiCx--4dDWnxa4qLOzEenKoJtaR2H2KvfLc9eEEw@mail.gmail.com>

Yes. I think so.

However, I found the V3 just contains partial of the patch. It is hard to find some V2 and some V3.
Also this series includes multiple package. We need different package maintainer to push different patches.

I recommend we do in this way:
Please split this big one into 3 - BaseTool patch, ArmPkg patch, and StandaloneMmPkg patch.

Then BaseTool maintainer can push BaseTool patch, ArmPkg maintainer can push ArmPkg patch, and I can help push StandaloneMmPkg patch.

Thank you
Yao Jiewen

> -----Original Message-----
> From: Thomas Abraham [mailto:thomas.abraham@arm.com]
> Sent: Monday, June 18, 2018 6:07 AM
> To: Sughosh Ganu <sng.lists@gmail.com>
> Cc: Supreeth Venkatesh <supreeth.venkatesh@arm.com>;
> edk2-devel@lists.01.org; Yao, Jiewen <jiewen.yao@intel.com>; Gao, Liming
> <liming.gao@intel.com>
> Subject: Re: [edk2] [PATCH v3 00/17] *** Standalone Management Mode Core
> Interface for AARCH64 Platforms ***
> 
> On Wed, Jun 6, 2018 at 4:50 PM, Sughosh Ganu <sng.lists@gmail.com> wrote:
> > On Tue, Jun 5, 2018 at 3:43 AM, Supreeth Venkatesh
> > <supreeth.venkatesh@arm.com> wrote:
> >> ***
> >> This patchset v3 contains only the patches that got feedback/comments
> frome the previous revision v2.
> >> The patches are
> >> [PATCH v3 06/17] StandaloneMmPkg: Delete StandaloneMmPkg file.
> >> [PATCH v3 13/17] StandaloneMmPkg: Add an AArch64 specific entry point
> library.
> >> [PATCH v3 17/17] BaseTools/AutoGen: Update header file for MM modules.
> >>
> >> Changes Since v2:
> >> (*) Address feedback provided for the commit "BaseTools/AutoGen: Update
> header file for MM modules."
> >> (*) Edit parameters for the StandaloneMmCpu Driver in the commit
> "StandaloneMmPkg: Add an AArch64 specific entry point library."
> >>
> >> Changes Since v1:
> >> (*) Reorder and Reword commits.
> >> (*) Reorganize structure of StandaloneMmPkg and rename libraries.
> >> (*) Address Review Comments from Achin, Jiewen and Daniil.
> >> ***
> >> Supreeth Venkatesh (17):
> >>   ArmPkg: Add PCDs needed for MM communication driver.
> >>   ArmPkg/Drivers: Add EFI_MM_COMMUNICATION_PROTOCOL DXE driver.
> >>   ArmPkg/Include: Add MM interface SVC return codes.
> >>   ArmPkg/ArmMmuLib: Add MMU Library suitable for use in S-EL0.
> >>   ArmPkg/ArmMmuLib: Add MMU library inf file suitable for use in S-EL0.
> >>   StandaloneMmPkg: Delete StandaloneMmPkg file.
> >>   StandaloneMmPkg/FvLib: Add a common FV Library for management
> mode.
> >>   StandaloneMmPkg/MemLib: Add Standalone MM instance of memory
> check
> >>     library.
> >>   StandaloneMmPkg/MemoryAllocationLib: Add MM memory allocation
> library.
> >>   StandaloneMmPkg/HobLib: Add HOB Library for management mode.
> >>   StandaloneMmPkg: MM driver entry point library.
> >>   StandaloneMmPkg/Core: Implementation of Standalone MM Core
> Module.
> >>   StandaloneMmPkg: Add an AArch64 specific entry point library.
> >>   StandaloneMmPkg: Add CPU driver suitable for ARM Platforms.
> >>   StandaloneMmPkg: Describe the declaration and definition files.
> >>   ArmPkg: Extra action to update permissions for S-ELO MM Image.
> >>   BaseTools/AutoGen: Update header file for MM modules.
> >
> > Tested all changes for RAS error injection and error handling on
> > SGI575 platform.
> >
> > Tested-by: Sughosh Ganu <sughosh.ganu@arm.com>
> >
> > -sughosh
> 
> There have been no further comments on this series. Can this patch
> series be merged?
> 
> Thanks,
> Thomas.

  reply	other threads:[~2018-06-18 15:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 22:13 [PATCH v3 00/17] *** Standalone Management Mode Core Interface for AARCH64 Platforms *** Supreeth Venkatesh
2018-06-04 22:13 ` [PATCH v3 06/17] StandaloneMmPkg: Delete StandaloneMmPkg file Supreeth Venkatesh
2018-06-04 22:13 ` [PATCH v3 13/17] StandaloneMmPkg: Add an AArch64 specific entry point library Supreeth Venkatesh
2018-06-04 22:13 ` [PATCH v3 17/17] BaseTools/AutoGen: Update header file for MM modules Supreeth Venkatesh
2018-06-05  5:37   ` Gao, Liming
2018-06-06 11:20 ` [PATCH v3 00/17] *** Standalone Management Mode Core Interface for AARCH64 Platforms *** Sughosh Ganu
2018-06-06 16:05   ` Supreeth Venkatesh
2018-06-18 13:07   ` Thomas Abraham
2018-06-18 15:12     ` Yao, Jiewen [this message]
2018-06-19  8:23       ` Achin Gupta
2018-06-20  1:56         ` Yao, Jiewen

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=74D8A39837DF1E4DA445A8C0B3885C503AC4EE35@shsmsx102.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