From: Ruiyu Ni <ruiyu.ni@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH 0/5] Change "dh" to support dump from GUID and "decode" parameter
Date: Mon, 9 Jan 2017 17:30:47 +0800 [thread overview]
Message-ID: <20170109093052.140504-1-ruiyu.ni@intel.com> (raw)
Change "dh" to support dump from GUID and "decode" parameter
Chen A Chen (2):
ShellPkg/HandleParsingLib: Add new API GetAllMappingGuids
ShellPkg/Dh: Fix coding style issues
Ruiyu Ni (3):
ShellPkg/HandleParsingLib: Rename global variables
ShellPkg/HandleParsingLib: Return NULL name for unknown GUID
ShellPkg/dh: Support dump from GUID and "decode" parameter
ShellPkg/Include/Library/HandleParsingLib.h | 21 +-
.../UefiHandleParsingLib/UefiHandleParsingLib.c | 130 ++++--
.../UefiHandleParsingLib/UefiHandleParsingLib.uni | 4 +-
ShellPkg/Library/UefiShellDriver1CommandsLib/Dh.c | 458 +++++++++++++++------
.../UefiShellDriver1CommandsLib.uni | 9 +-
5 files changed, 446 insertions(+), 176 deletions(-)
--
2.9.0.windows.1
next reply other threads:[~2017-01-09 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 9:30 Ruiyu Ni [this message]
2017-01-09 9:30 ` [PATCH 1/5] ShellPkg/HandleParsingLib: Rename global variables Ruiyu Ni
2017-01-09 9:30 ` [PATCH 2/5] ShellPkg/HandleParsingLib: Return NULL name for unknown GUID Ruiyu Ni
2017-01-09 9:30 ` [PATCH 3/5] ShellPkg/HandleParsingLib: Add new API GetAllMappingGuids Ruiyu Ni
2017-01-09 9:30 ` [PATCH 4/5] ShellPkg/Dh: Fix coding style issues Ruiyu Ni
2017-01-09 15:36 ` Carsey, Jaben
2017-01-10 2:24 ` Ni, Ruiyu
2017-01-10 16:20 ` Carsey, Jaben
2017-01-09 9:30 ` [PATCH 5/5] ShellPkg/dh: Support dump from GUID and "decode" parameter Ruiyu Ni
2017-01-09 15:40 ` [PATCH 0/5] Change "dh" to support " Carsey, Jaben
2017-01-10 2:23 ` Ni, Ruiyu
2017-01-10 21:43 ` Carsey, Jaben
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=20170109093052.140504-1-ruiyu.ni@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