From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/2] ShellPkg/memmap: Dump memory map information for all memory types
Date: Thu, 11 May 2017 16:23:22 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C630B3E24@fmsmsx101.amr.corp.intel.com> (raw)
In-Reply-To: <20170511102706.89404-1-ruiyu.ni@intel.com>
For series.
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Ruiyu Ni
> Sent: Thursday, May 11, 2017 3:27 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH 0/2] ShellPkg/memmap: Dump memory map
> information for all memory types
> Importance: High
>
> The patch dumps memory map information for all memory types.
> But to follow the SFO format of "memmap" defined in Shell 2.2 spec,
> the patch doesn't dump the memory map information for OEM/OS
> memory types. But it does include the OEM/OS memory in the total
> size in SFO format.
>
> Ruiyu Ni (2):
> ShellPkg/memmap: Refine code
> ShellPkg/memmap: Dump memory map information for all memory types
>
> .../Library/UefiShellDebug1CommandsLib/MemMap.c | 199
> +++++++++++++++------
> .../UefiShellDebug1CommandsLib.uni | 4 +-
> 2 files changed, 148 insertions(+), 55 deletions(-)
>
> --
> 2.12.2.windows.2
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-05-11 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 10:27 [PATCH 0/2] ShellPkg/memmap: Dump memory map information for all memory types Ruiyu Ni
2017-05-11 10:27 ` [PATCH 1/2] ShellPkg/memmap: Refine code Ruiyu Ni
2017-05-11 10:27 ` [PATCH 2/2] ShellPkg/memmap: Dump memory map information for all memory types Ruiyu Ni
2017-05-11 16:23 ` Carsey, Jaben [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=CB6E33457884FA40993F35157061515C630B3E24@fmsmsx101.amr.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