public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Eric Dong <eric.dong@intel.com>
To: edk2-devel@lists.01.org
Cc: Jeff Fan <jeff.fan@intel.com>, Ruiyu Ni <ruiyu.ni@intel.com>
Subject: [Patch 1/2] MdePkg SmmAccess2: Update comments to follow PI spec.
Date: Wed, 19 Jul 2017 10:37:34 +0800	[thread overview]
Message-ID: <1500431855-11084-2-git-send-email-eric.dong@intel.com> (raw)
In-Reply-To: <1500431855-11084-1-git-send-email-eric.dong@intel.com>

Cc: Jeff Fan <jeff.fan@intel.com>
Cc: Ruiyu Ni <ruiyu.ni@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Eric Dong <eric.dong@intel.com>
---
 MdePkg/Include/Protocol/SmmAccess2.h | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/MdePkg/Include/Protocol/SmmAccess2.h b/MdePkg/Include/Protocol/SmmAccess2.h
index eb315db..5904266 100644
--- a/MdePkg/Include/Protocol/SmmAccess2.h
+++ b/MdePkg/Include/Protocol/SmmAccess2.h
@@ -108,8 +108,9 @@ EFI_STATUS
 
 ///
 ///  EFI SMM Access2 Protocol is used to control the visibility of the SMRAM on the platform.
-///  It abstracts the location and characteristics of SMRAM.  The expectation is
-///  that the north bridge or memory controller would publish this protocol.
+///  It abstracts the location and characteristics of SMRAM. The platform should report all 
+///  MMRAM via EFI_MM_ACCESS_PROTOCOL. The expectation is that the north bridge or memory 
+///  controller would publish this protocol.
 /// 
 struct _EFI_SMM_ACCESS2_PROTOCOL {
   EFI_SMM_OPEN2          Open;
-- 
2.7.0.windows.1



  reply	other threads:[~2017-07-19  2:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19  2:37 [Patch 0/2] Update comments to follow spec update Eric Dong
2017-07-19  2:37 ` Eric Dong [this message]
2017-07-19  2:59   ` [Patch 1/2] MdePkg SmmAccess2: Update comments to follow PI spec Ni, Ruiyu
2017-07-19  2:37 ` [Patch 2/2] MdeModulePkg SmmAccess: " Eric Dong
2017-07-19  2:59   ` Ni, Ruiyu

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=1500431855-11084-2-git-send-email-eric.dong@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