From: "Gao, Liming" <liming.gao@intel.com>
To: "Dong, Eric" <eric.dong@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch] SecurityPkg/OpalPassword: Fix incorrect line ending issue.
Date: Mon, 18 Mar 2019 00:52:49 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E40496C@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190301023357.2332-1-eric.dong@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Eric
>Dong
>Sent: Friday, March 01, 2019 10:34 AM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming <liming.gao@intel.com>
>Subject: [edk2] [Patch] SecurityPkg/OpalPassword: Fix incorrect line ending
>issue.
>
>Cc: Liming Gao <liming.gao@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Eric Dong <eric.dong@intel.com>
>---
> SecurityPkg/Tcg/Opal/OpalPassword/OpalHiiCallbacks.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/SecurityPkg/Tcg/Opal/OpalPassword/OpalHiiCallbacks.c
>b/SecurityPkg/Tcg/Opal/OpalPassword/OpalHiiCallbacks.c
>index 6d1a3a9b25..a1802313c3 100644
>--- a/SecurityPkg/Tcg/Opal/OpalPassword/OpalHiiCallbacks.c
>+++ b/SecurityPkg/Tcg/Opal/OpalPassword/OpalHiiCallbacks.c
>@@ -115,4 +115,4 @@ HiiDiskGetNameCB(
> return Ctx->NameZ;
> }
> return NULL;
>-}
>\ No newline at end of file
>+}
>\ No newline at end of file
>--
>2.15.0.windows.1
>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2019-03-18 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 2:33 [Patch] SecurityPkg/OpalPassword: Fix incorrect line ending issue Eric Dong
2019-03-18 0:52 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E40496C@SHSMSX104.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