public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: "Tian, Feng" <feng.tian@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>, "Jin, Eric" <eric.jin@intel.com>
Subject: Re: [patch] MdePkg: Fix spec mismatch in string representation of EMMC dev node
Date: Fri, 11 Nov 2016 08:45:42 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D58E73CE2@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <28ff970e51883b4afa23a164c34b1cad295e76c5.1478755004.git.feng.tian@intel.com>

Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>

Thanks/Ray

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Feng Tian
> Sent: Thursday, November 10, 2016 1:17 PM
> To: edk2-devel@lists.01.org
> Cc: Gao, Liming <liming.gao@intel.com>; Jin, Eric <eric.jin@intel.com>
> Subject: [edk2] [patch] MdePkg: Fix spec mismatch in string representation
> of EMMC dev node
> 
> Cc: Eric Jin <eric.jin@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Feng Tian <feng.tian@intel.com>
> ---
>  MdePkg/Library/UefiDevicePathLib/DevicePathFromText.c | 2 +-
>  MdePkg/Library/UefiDevicePathLib/DevicePathToText.c   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/MdePkg/Library/UefiDevicePathLib/DevicePathFromText.c
> b/MdePkg/Library/UefiDevicePathLib/DevicePathFromText.c
> index c167b4c..8a3a470 100644
> --- a/MdePkg/Library/UefiDevicePathLib/DevicePathFromText.c
> +++ b/MdePkg/Library/UefiDevicePathLib/DevicePathFromText.c
> @@ -3529,7 +3529,7 @@ GLOBAL_REMOVE_IF_UNREFERENCED
> DEVICE_PATH_FROM_TEXT_TABLE mUefiDevicePathLibDevP
>    {L"NVMe",                    DevPathFromTextNVMe                    },
>    {L"UFS",                     DevPathFromTextUfs                     },
>    {L"SD",                      DevPathFromTextSd                      },
> -  {L"Emmc",                    DevPathFromTextEmmc                    },
> +  {L"eMMC",                    DevPathFromTextEmmc                    },
>    {L"DebugPort",               DevPathFromTextDebugPort               },
>    {L"MAC",                     DevPathFromTextMAC                     },
>    {L"IPv4",                    DevPathFromTextIPv4                    },
> diff --git a/MdePkg/Library/UefiDevicePathLib/DevicePathToText.c
> b/MdePkg/Library/UefiDevicePathLib/DevicePathToText.c
> index 5922dee..87eca23 100644
> --- a/MdePkg/Library/UefiDevicePathLib/DevicePathToText.c
> +++ b/MdePkg/Library/UefiDevicePathLib/DevicePathToText.c
> @@ -850,7 +850,7 @@ DevPathToTextEmmc (
>    Emmc = DevPath;
>    UefiDevicePathLibCatPrint (
>      Str,
> -    L"Emmc(0x%x)",
> +    L"eMMC(0x%x)",
>      Emmc->SlotNumber
>      );
>  }
> --
> 2.7.1.windows.2
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2016-11-11  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10  5:17 [patch] MdePkg: Fix spec mismatch in string representation of EMMC dev node Feng Tian
2016-11-11  8:45 ` Ni, Ruiyu [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=734D49CCEBEEF84792F5B80ED585239D58E73CE2@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