From: "Tian, Feng" <feng.tian@intel.com>
To: "Bi, Dandan" <dandan.bi@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Tian, Feng" <feng.tian@intel.com>
Subject: Re: [patch 1/2] MdeModulePkg/MemoryProtection: Fix coding style issue
Date: Tue, 28 Mar 2017 06:43:39 +0000 [thread overview]
Message-ID: <7F1BAD85ADEA444D97065A60D2E97EE5699CF888@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1490662895-69668-1-git-send-email-dandan.bi@intel.com>
Reviewed-by: Feng Tian <feng.tian@intel.com>
Thanks
Feng
-----Original Message-----
From: Bi, Dandan
Sent: Tuesday, March 28, 2017 9:02 AM
To: edk2-devel@lists.01.org
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>; Tian, Feng <feng.tian@intel.com>
Subject: [patch 1/2] MdeModulePkg/MemoryProtection: Fix coding style issue
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Feng Tian <feng.tian@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Dandan Bi <dandan.bi@intel.com>
---
MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c b/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
index 93f96f0..a73c4cc 100644
--- a/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
+++ b/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
@@ -382,11 +382,11 @@ FreeImageRecord (
}
FreePool (ImageRecord);
}
/**
- Protect UEFI PE/COFF image
+ Protect UEFI PE/COFF image.
@param[in] LoadedImage The loaded image protocol
@param[in] LoadedImageDevicePath The loaded image device path protocol
**/
VOID
--
1.9.5.msysgit.1
prev parent reply other threads:[~2017-03-28 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 1:01 [patch 1/2] MdeModulePkg/MemoryProtection: Fix coding style issue Dandan Bi
2017-03-28 1:01 ` [patch 2/2] ShellPkg/Shell: Make comments align with the function Dandan Bi
2017-03-28 2:16 ` Ni, Ruiyu
2017-03-28 6:43 ` Tian, Feng [this message]
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=7F1BAD85ADEA444D97065A60D2E97EE5699CF888@SHSMSX101.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