public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Sughosh Ganu <sng.lists@gmail.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Supreeth Venkatesh <supreeth.venkatesh@arm.com>, edk2-devel@lists.01.org
Subject: Re: [PATCH 2/6] ArmPkg/Drivers: Add EFI_MM_COMMUNICATION_PROTOCOL DXE driver.
Date: Mon, 9 Jul 2018 14:05:32 +0530	[thread overview]
Message-ID: <CAHxXkBem2ocOPQ91wR9QOudoUWSyZkhOZx83NAV1yvyO2AZ=GA@mail.gmail.com> (raw)
In-Reply-To: <20180703141206.xyqthexlyucxknoo@bivouac.eciton.net>

hi Leif,

On Tue, Jul 3, 2018 at 7:42 PM, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> On Tue, Jul 03, 2018 at 03:25:11PM +0530, Supreeth Venkatesh wrote:
>> PI v1.5 Specification Volume 4 defines Management Mode Core Interface
>> and defines EFI_MM_COMMUNICATION_PROTOCOL. This protocol provides a
>> means of communicating between drivers outside of MM and MMI
>> handlers inside of MM.
>>
>> This patch implements the EFI_MM_COMMUNICATION_PROTOCOL DXE runtime
>> driver for AARCH64 platforms. It uses SMCs allocated from the standard
>> SMC range defined in DEN0060A_ARM_MM_Interface_Specification.pdf
>
> I would prefer the document to be referred to by its official name and
> its document number:
> ARM Management Mode Interface Specification (ARM DEN0060A)
>
>> to communicate with the standalone MM environment in the secure world.
>>
>> This patch also adds the MM Communication driver (.inf) file to
>> define entry point for this driver and other compile
>> related information the driver needs.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Achin Gupta <achin.gupta@arm.com>
>> Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
>
> Oh, and only one Signed-off-by per patch please.
> If authorship is to be indicated, ensure that's correct in git before
> calling format-patch.

Supreeth has moved onto some other work, hence I will be working on
the upstreaming of these patches henceforth. Will handle your comments
on all the patches and send an updated version. Regarding the
inclusion of a single Signed-off-By, i have a doubt. Work on these
patches was initially done by Achin, and then Supreeth. I will be
handling your review comments and posting the updated version. You
have posted a comment saying that we can have only a single s-o-b in
any given patch. In such a scenario, how can we attribute the work
done by all the engineers for these patches. Can you please let me
know on this. As per my understanding, other projects do allow
multiple s-o-b's per patch. Thanks.

-sughosh


  reply	other threads:[~2018-07-09  8:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03  9:55 [PATCH 0/6] ArmPkg related changes for StandaloneMM package Supreeth Venkatesh
2018-07-03  9:55 ` [PATCH 1/6] ArmPkg: Add PCDs needed for MM communication driver Supreeth Venkatesh
2018-07-03 12:09   ` Leif Lindholm
2018-07-03  9:55 ` [PATCH 2/6] ArmPkg/Drivers: Add EFI_MM_COMMUNICATION_PROTOCOL DXE driver Supreeth Venkatesh
2018-07-03 14:12   ` Leif Lindholm
2018-07-09  8:35     ` Sughosh Ganu [this message]
2018-07-09  9:45       ` Leif Lindholm
2018-07-03  9:55 ` [PATCH 3/6] ArmPkg/Include: Add MM interface SVC return codes Supreeth Venkatesh
2018-07-03 10:44   ` Leif Lindholm
2018-07-03  9:55 ` [PATCH 4/6] ArmPkg/ArmMmuLib: Add MMU Library suitable for use in S-EL0 Supreeth Venkatesh
2018-07-03 14:28   ` Leif Lindholm
2018-07-03  9:55 ` [PATCH 5/6] ArmPkg/ArmMmuLib: Add MMU library inf file " Supreeth Venkatesh
2018-07-03  9:55 ` [PATCH 6/6] ArmPkg: Extra action to update permissions for S-ELO MM Image Supreeth Venkatesh
2018-07-03 14:35   ` Leif Lindholm

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='CAHxXkBem2ocOPQ91wR9QOudoUWSyZkhOZx83NAV1yvyO2AZ=GA@mail.gmail.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