public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Zhichao" <zhichao.gao@intel.com>
To: devel@edk2.groups.io
Cc: Laszlo Ersek <lersek@redhat.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <liming.gao@intel.com>,
	Dandan Bi <dandan.bi@intel.com>
Subject: [PATCH V3 4/8] IntelFrameworkModulePkg: make global variable static
Date: Fri, 26 Apr 2019 09:04:00 +0800	[thread overview]
Message-ID: <20190426010404.20624-5-zhichao.gao@intel.com> (raw)
In-Reply-To: <20190426010404.20624-1-zhichao.gao@intel.com>

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1740

Add a 'static' storage-class specifier to the global variables
that only used in a single file to minimize the name collisions.
This is only for the variable named 'mExitBootServicesEvent'.

Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Dandan Bi <dandan.bi@intel.com>
Signed-off-by: Zhichao Gao <zhichao.gao@intel.com>
---
 .../DatahubStatusCodeHandlerDxe/DatahubStatusCodeHandlerDxe.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/IntelFrameworkModulePkg/Universal/StatusCode/DatahubStatusCodeHandlerDxe/DatahubStatusCodeHandlerDxe.c b/IntelFrameworkModulePkg/Universal/StatusCode/DatahubStatusCodeHandlerDxe/DatahubStatusCodeHandlerDxe.c
index 0f9185144d..5a82b99d09 100644
--- a/IntelFrameworkModulePkg/Universal/StatusCode/DatahubStatusCodeHandlerDxe/DatahubStatusCodeHandlerDxe.c
+++ b/IntelFrameworkModulePkg/Universal/StatusCode/DatahubStatusCodeHandlerDxe/DatahubStatusCodeHandlerDxe.c
@@ -2,14 +2,14 @@
   Status Code Handler Driver which produces datahub handler and hook it
   onto the DXE status code router.
 
-  Copyright (c) 2010 - 2018, Intel Corporation. All rights reserved.<BR>
+  Copyright (c) 2010 - 2019, Intel Corporation. All rights reserved.<BR>
   SPDX-License-Identifier: BSD-2-Clause-Patent
 
 **/
 
 #include "DatahubStatusCodeHandlerDxe.h"
 
-EFI_EVENT                 mExitBootServicesEvent     = NULL;
+static EFI_EVENT          mExitBootServicesEvent     = NULL;
 EFI_RSC_HANDLER_PROTOCOL  *mRscHandlerProtocol       = NULL;
 
 /**
-- 
2.21.0.windows.1


  parent reply	other threads:[~2019-04-26  1:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  1:03 [PATCH V3 0/8] make mExitBootServicesEvent static Gao, Zhichao
2019-04-26  1:03 ` [PATCH V3 1/8] MdePkg/UefiDebugLibConOut: make global variable static Gao, Zhichao
2019-04-26  1:03 ` [PATCH V3 2/8] MdePkg/UefiDebugLibDebugPortProtocol: " Gao, Zhichao
2019-04-26  1:03 ` [PATCH V3 3/8] MdePkg/UefiDebugLibStdErr: " Gao, Zhichao
2019-04-26  1:04 ` Gao, Zhichao [this message]
2019-04-26  1:04 ` [PATCH V3 5/8] MdeModulePkg/FirmwarePerformanceDxe: " Gao, Zhichao
2019-04-26  5:58   ` [edk2-devel] " Wu, Hao A
2019-04-26  8:11     ` Gao, Zhichao
2019-04-26  8:30       ` Wu, Hao A
2019-04-26 19:37         ` Laszlo Ersek
2019-04-26  1:04 ` [PATCH V3 6/8] IntelFsp2WrapperPkg/FspWrapperNotifyDxe: " Gao, Zhichao
2019-04-26  1:36   ` Chiu, Chasel
2019-04-26  1:04 ` [PATCH V3 7/8] IntelFrameworkModulePkg: " Gao, Zhichao
2019-04-26  1:04 ` [PATCH V3 8/8] MdeModulePkg/StatusCodeHandlerRuntimeDxe: " Gao, Zhichao
2019-04-26  6:00   ` Wu, Hao A
2019-04-26 19:37 ` [PATCH V3 0/8] make mExitBootServicesEvent static Laszlo Ersek
2019-04-28  1:30   ` Liming Gao

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=20190426010404.20624-5-zhichao.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