public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Liming Gao <liming.gao@intel.com>
To: edk2-devel@lists.01.org
Cc: Ruiyu Ni <ruiyu.ni@intel.com>
Subject: [Patch 03/11] PcAtChipsetPkg: Update GUID usage in PcRtc INF to match the source code
Date: Mon, 25 Sep 2017 19:06:16 +0800	[thread overview]
Message-ID: <1506337584-9588-4-git-send-email-liming.gao@intel.com> (raw)
In-Reply-To: <1506337584-9588-1-git-send-email-liming.gao@intel.com>

Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Liming Gao <liming.gao@intel.com>
Cc: Ruiyu Ni <ruiyu.ni@intel.com>
---
 .../PcatRealTimeClockRuntimeDxe/PcatRealTimeClockRuntimeDxe.inf  | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcatRealTimeClockRuntimeDxe.inf b/PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcatRealTimeClockRuntimeDxe.inf
index 8b992d0..dd746a2 100644
--- a/PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcatRealTimeClockRuntimeDxe.inf
+++ b/PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcatRealTimeClockRuntimeDxe.inf
@@ -58,8 +58,13 @@
   gEfiRealTimeClockArchProtocolGuid             ## PRODUCES
 
 [Guids]
-  gEfiAcpi10TableGuid                           ## CONSUMES ## Event
-  gEfiAcpiTableGuid                             ## CONSUMES ## Event
+  ## SOMETIMES_CONSUMES ## Event
+  ## SOMETIMES_CONSUMES ## SystemTable
+  gEfiAcpi10TableGuid
+
+  ## SOMETIMES_CONSUMES ## Event
+  ## SOMETIMES_CONSUMES ## SystemTable
+  gEfiAcpiTableGuid
 
 [Depex]
   gEfiVariableArchProtocolGuid AND gEfiVariableWriteArchProtocolGuid
-- 
2.8.0.windows.1



  parent reply	other threads:[~2017-09-25 11:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 11:06 [Patch 00/11] Correct Ppi/Protocol/Guid usage in module INF files Liming Gao
2017-09-25 11:06 ` [Patch 01/11] MdePkg: Correct BaseS3PciSegmentLib module name to match its uni file Liming Gao
2017-09-25 12:48   ` Ni, Ruiyu
2017-09-25 11:06 ` [Patch 02/11] FatPkg: Update Ppi/Protocol usage in Fat INF to match source code logic Liming Gao
2017-09-25 12:44   ` Ni, Ruiyu
2017-09-26  3:27     ` Gao, Liming
2017-09-25 11:06 ` Liming Gao [this message]
2017-09-25 12:46   ` [Patch 03/11] PcAtChipsetPkg: Update GUID usage in PcRtc INF to match the source code Ni, Ruiyu
2017-09-25 11:06 ` [Patch 04/11] UefiCpuPkg: Update Guid usage in DxeMpInitLib INF to match source code logic Liming Gao
2017-09-25 12:08   ` Dong, Eric
2017-09-25 11:06 ` [Patch 05/11] ShellPkg: Update Guid usage in ShellLib " Liming Gao
2017-09-25 12:47   ` Ni, Ruiyu
2017-09-25 11:06 ` [Patch 06/11] NetworkPkg: Update Protocol/Guid usage in INF file " Liming Gao
2017-09-26  0:41   ` Fu, Siyuan
2017-10-10  7:24   ` Wu, Jiaxin
2017-09-25 11:06 ` [Patch 07/11] SignedCapsulePkg: Update Guid " Liming Gao
2017-10-10  6:58   ` Yao, Jiewen
2017-09-25 11:06 ` [Patch 08/11] SecurityPkg: " Liming Gao
2017-10-10  8:39   ` Zhang, Chao B
2017-09-25 11:06 ` [Patch 09/11] IntelFsp2Pkg: Update Section Name in INF files Liming Gao
2017-10-10  6:58   ` Yao, Jiewen
2017-09-25 11:06 ` [Patch 10/11] IntelFsp2WrapperPkg: Update Protocol/Guid usage " Liming Gao
2017-10-10  6:58   ` Yao, Jiewen
2017-09-25 11:06 ` [Patch 11/11] MdeModulePkg: Update Ppi/Protocol/Guid " Liming Gao
2017-09-25 11:18   ` Zeng, Star

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=1506337584-9588-4-git-send-email-liming.gao@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