From: "Gao, Liming" <liming.gao@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH v2 0/2] Add NVDIMM related spec definitions
Date: Wed, 8 Nov 2017 08:24:26 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E179FC5@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20171108063308.227984-1-ruiyu.ni@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
>Ruiyu Ni
>Sent: Wednesday, November 08, 2017 2:33 PM
>To: edk2-devel@lists.01.org
>Subject: [edk2] [PATCH v2 0/2] Add NVDIMM related spec definitions
>
>v2:
> 1. Create Btt.h in Include/Guid directory per Liming's comments.
> 2. Change the GUID C name to match macro name.
>
>Ruiyu Ni (2):
> MdePkg/Btt.h: Add Block Translation Table definitions
> MdePkg/NvdimmLabel.h: Add NVDIMM_LABEL protocol definition
>
> MdePkg/Include/Guid/Btt.h | 228 ++++++++++++++++++++++
> MdePkg/Include/Protocol/NvdimmLabel.h | 351
>++++++++++++++++++++++++++++++++++
> MdePkg/MdePkg.dec | 9 +
> 3 files changed, 588 insertions(+)
> create mode 100644 MdePkg/Include/Guid/Btt.h
> create mode 100644 MdePkg/Include/Protocol/NvdimmLabel.h
>
>--
>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-11-08 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 6:33 [PATCH v2 0/2] Add NVDIMM related spec definitions Ruiyu Ni
2017-11-08 6:33 ` [PATCH v2 1/2] MdePkg/Btt.h: Add Block Translation Table definitions Ruiyu Ni
2017-11-08 6:33 ` [PATCH v2 2/2] MdePkg/NvdimmLabel.h: Add NVDIMM_LABEL protocol definition Ruiyu Ni
2017-11-08 8:24 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E179FC5@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